Just to pile on, transaction logs do use up some memory, but it does
NOT store the whole document in memory, docs are flushed to the tlog
on disk. What is kept in memory is some basic doc info (unique id?)
and a pointer to that doc in memory, so not much really unless you're
keeping a boatload of d
: > However, we are wondering how to best setup autoCommit/autoSoftCommit on
: > masters to preserve the old behavior. It seems that setting autoCommit to
: > 1hr (openSearcher=true) without any autoSoftCommit preserves our previous
: > setup - is this correct? Wil the transaction log make masters
On 6/11/2013 4:07 PM, Michael Tsadikov wrote:
Thanks for the quick reply, Shawn.
I am less worried about long transaction-log replays after crashes because
in normal life (long uptimes, rare orderly restarts) this should never
happen, and even if it does, uses will not be affected.
I am more wo
Thanks for the quick reply, Shawn.
I am less worried about long transaction-log replays after crashes because
in normal life (long uptimes, rare orderly restarts) this should never
happen, and even if it does, uses will not be affected.
I am more worried about potential increase in heap usage due
On 6/11/2013 3:45 PM, Michael Tsadikov wrote:
We're upgrading our Solr 3.1 distributed masters/slaves setup to 4.3.
In 3.1 we used autoCommit every hour on masters, each commit is replicated
to slaves, and all searches are done on slaves. 1hr visibility is ok - we
don't need NRT.
In 4.3 we enab
