Yes, you must issue hard commits. You can use autocommit and use openSearcher=false. Autocommit is not distributed, it has to be configured in every node (which will automatically be, because you are using the exact same solrconfig for all your nodes).
Other option is to issue an explicit hard commit command, those ARE distributed across all shards and replicas. You should also use "openSearcher=false" option for explicit hard commits (the searcher is now being opened by the soft commits). Both options are fine. Personally I prefer autocommit because then you can just "forget" about commits. Tomás On Thu, Jan 10, 2013 at 7:51 AM, gadde <gadde....@gmail.com> wrote: > we have a SolrCloud with 3 nodes. we add documents to leader node and use > commitwithin(100secs) option in SolrJ to add documents. AutoSoftCommit in > SolrConfig is 1000ms. > > Transaction logs on replicas grew bigger than the index and we ran out of > disk space in few days. Leader's tlogs are very small in few hundred MBs. > > The following post suggest hard commit is required for "relieving the > memory > pressure of the transactionlog" > > http://lucene.472066.n3.nabble.com/SolrCloud-is-softcommit-cluster-wide-for-the-collection-td4021584.html#a4021631 > > what is the best way to do a hard commit on this setup in SolrCloud? > > a. Through autoCommit in SolrConfig? which would cause hard commit on all > the nodes at different times > b. Trigger hard commit on leader while updating through SolrJ? > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Large-transaction-logs-tp4032144.html > Sent from the Solr - User mailing list archive at Nabble.com. >
