right, suggester had some bad behavior where it rebuilt on startup despite setting the flag to _not_ do that. See:
Some details here: https://lucidworks.com/blog/2015/03/04/solr-suggester/ Best, Erick On Tue, Jan 12, 2016 at 8:12 AM, Matteo Grolla <matteo.gro...@gmail.com> wrote: > ok, > suggester was responsible for the long time to load. > Thanks > > 2016-01-12 15:47 GMT+01:00 Matteo Grolla <matteo.gro...@gmail.com>: > >> Thanks Shawn, >> On a production solr instance some cores take a long time to load >> while other of similar size take much less. One of the differences between >> these cores is the directoryFactory. >> >> 2016-01-12 15:34 GMT+01:00 Shawn Heisey <apa...@elyograg.org>: >> >>> On 1/12/2016 2:50 AM, Matteo Grolla wrote: >>> > and that it works with any directory factory? (Not just >>> > NRTCachingDirectoryFactory) >>> >>> Realtime Get relies on the updateLog to return uncommitted documents, >>> and standard Lucene mechanisms to return documents that have already >>> been committed. It should work with any directory. >>> >>> I would like to know why you're changing the directory. The only time >>> the directory should be changed is if you want to work with something >>> exotic like HDFS. With a typical installation using a typical >>> filesystem, NRTCachingDirectoryFactory is absolutely the best option and >>> should not be replaced with anything else. The NRT factory uses MMap, >>> so there is no need to switch to MMapDirectoryFactory. >>> >>> Thanks, >>> Shawn >>> >>> >>
