lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Shalin Shekhar Mangar <shalinman...@gmail.com>
Subject Re: Solr tlog and soft commit
Date Tue, 17 Mar 2015 22:03:56 GMT
When you issue an atomic update request, Solr needs to lookup the stored
fields of the last document that you have added, process it according to
your atomic update and then index that document again (replacing the old
one).

If you send an atomic update request before the old document was committed
to the index then it has to be looked up from the transaction logs.

On Tue, Mar 17, 2015 at 12:47 PM, vidit.asthana <vidit.asthana7@gmail.com>
wrote:

> Should I open a JIRA, in case there is no explanation of why all of a
> sudden
> transaction logs start piling up for some shard/replica?
>
> I have provided very detailed explanation in a different thread:
>
> http://lucene.472066.n3.nabble.com/Transaction-logs-not-getting-deleted-td4184635.html
>
> Also can someone explain in what way tlogs gets involved while sending a
> atomic update request?
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/Solr-tlog-and-soft-commit-tp4193105p4193559.html
> Sent from the Solr - User mailing list archive at Nabble.com.
>



-- 
Regards,
Shalin Shekhar Mangar.

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message