i have 2 solr cores on a machine with same configs. Problem is I am getting faster indexing speed on core1 and slower on core2.
Both cores have same index size and configuration. On Tue, Aug 16, 2016 at 11:34 PM, Erick Erickson <erickerick...@gmail.com> wrote: > Why? What is the problem you're facing that you hope > understanding more about these will help? > > Here are two places to start: > http://blog.mikemccandless.com/2011/02/visualizing- > lucenes-segment-merges.html > https://lucidworks.com/blog/2013/08/23/understanding- > transaction-logs-softcommit-and-commit-in-sorlcloud/ > > In general every time you do a hard commit the Lucene index is checked > to see if there are segments that should be merged. If so, then a > background > thread is kicked off to start merging selected segments. Which segments > is decided by the MergePolicy in effect (TieredMergePolicy is the default). > > Best, > Erick > > On Tue, Aug 16, 2016 at 10:47 AM, kshitij tyagi > <kshitij.shopcl...@gmail.com> wrote: > > I need to understand clearly that is there any relationship between solr > > merging and solr commit? > > > > If there is then what is it? > > > > Also i need to understand how both of these affect indexing speed on the > > core? >
