On Mon, Dec 13, 2010 at 4:01 AM, Erick Erickson <erickerick...@gmail.com> wrote: > I'm shooting in the dark here, but according to this: > http://wiki.apache.org/solr/SolrReplication > <http://wiki.apache.org/solr/SolrReplication>after the slave pulls the index > down, it issues a commit. So if your > slave is configured to generate the dictionary on commit, will it > "just happen"?
Our slaves spellcheckers are not configured to buildOnCommit, therefore it shouldn't just happen. > > But according to this: https://issues.apache.org/jira/browse/SOLR-866 > <https://issues.apache.org/jira/browse/SOLR-866>this is an open issue.... Thanx for the pointer! SOLR-866 is even better suited for us - after reading SOLR-433 again I realized that it targets scripts based replication (what we're going to leave behind us). Cheers, Martin > > Best > Erick > > On Sun, Dec 12, 2010 at 8:30 PM, Martin Grotzke < > martin.grot...@googlemail.com> wrote: > >> On Mon, Dec 13, 2010 at 2:12 AM, Markus Jelsma >> <markus.jel...@openindex.io> wrote: >> > Maybe you've overlooked the build parameter? >> > http://wiki.apache.org/solr/SpellCheckComponent#spellcheck.build >> I'm aware of this, but we don't want to maintain cron-jobs on all >> slaves for all spellcheckers for all cores. >> That's why I'm thinking about a more integrated solution. Or did I >> really overlook s.th.? >> >> Cheers, >> Martin >> >> >> > >> >> Hi, >> >> >> >> the spellchecker component already provides a buildOnCommit and >> >> buildOnOptimize option. >> >> >> >> Since we have several spellchecker indices building on each commit is >> >> not really what we want to do. >> >> Building on optimize is not possible as index optimization is done on >> >> the master and the slaves don't even run an optimize but only fetch >> >> the optimized index. >> >> >> >> Therefore I'm thinking about an extension of the spellchecker that >> >> allows you to rebuild the spellchecker based on a cron-expression >> >> (e.g. rebuild each night at 1 am). >> >> >> >> What do you think about this, is there anybody else interested in this? >> >> >> >> Regarding the lifecycle, is there already some executor "framework" or >> >> any regularly running process in place, or would I have to pull up my >> >> own thread? If so, how can I stop my thread when solr/tomcat is >> >> shutdown (I couldn't see any shutdown or destroy method in >> >> SearchComponent)? >> >> >> >> Thanx for your feedback, >> >> cheers, >> >> Martin >> > >> >> >> >> -- >> Martin Grotzke >> http://twitter.com/martin_grotzke >> > -- Martin Grotzke http://www.javakaffee.de/blog/
