So does it make the most sense then to force, by default, facet.method=fcs on slave nodes that receive updates every 5 minutes but with large segments that don't change every update? Right now, everything I have configured uses facet.method=fc since we don't declare it at all.
Randomly, after replication, I have several threads that will hang on reading data from field cache and I'm trying to think of things I can do to mitigate that. Thanks for the info. > Hello Patrick, > > Replication flushes UnInvertedField cache that impacts fc, but doesn't > harm Lucene's FieldCache which is for fcs. You can check how much time > in millis is spend on UnInvertedField cache regeneration in INFO logs like > "UnInverted multi-valued field ....,time=### ..." > > > On Thu, Dec 5, 2013 at 12:15 AM, Patrick O'Lone <pol...@townnews.com > <mailto:pol...@townnews.com>> wrote: > > Is there any advantage on a Solr slave to receive queries using > facet.method=fcs instead of the default of facet.method=fc? Most of the > segment files are unchanged between replication events - but I wasn't > sure if replication would cause the unchanged segment field caches to be > lost anyway. > -- > Patrick O'Lone > Director of Software Development > TownNews.com > > E-mail ... pol...@townnews.com <mailto:pol...@townnews.com> > Phone .... 309-743-0809 > Fax ...... 309-743-0830 > > > > > -- > Sincerely yours > Mikhail Khludnev > Principal Engineer, > Grid Dynamics > > <http://www.griddynamics.com> > <mailto:mkhlud...@griddynamics.com> -- Patrick O'Lone Director of Software Development TownNews.com E-mail ... pol...@townnews.com Phone .... 309-743-0809 Fax ...... 309-743-0830
