2015-07-15 12:44 GMT+01:00 Markus Jelsma <markus.jel...@openindex.io>:
> Well yes, a simple empty commit won't do the trick, the searcher is not
> going to reload on recent versions. Reloading the core will.
>
mmm Markus, let's assume we trigger a soft commit, even empty, if open
searcher is equal true, it is not going to be forced ?
>From the DirectUpdateHandler2
…
if (cmd.openSearcher) {
core.getSearcher(true, false, waitSearcher);
…
It seems that :
forceNew if true, force the open of a new index searcher
regardless if there is already one open.
Am i wrong ? Am I missing anything ?
>
> -----Original message-----
> > From:Bernd Fehling <bernd.fehl...@uni-bielefeld.de>
> > Sent: Wednesday 15th July 2015 13:42
> > To: solr-user@lucene.apache.org
> > Subject: Re: To the experts: howto force opening a new searcher?
> >
> > What ever you name a problem, I just wanted to open a new searcher
> > after several days of heavy load/searching on one of my slaves
> > to do some testing with empty field-/document-/filter-caches.
>
Aren't you warming your caches on commits ? You always discard all the old
caches without warming them ?
> >
> > Sure, I could first add, then delete a document and do a commit.
> > Or may be only do a fake update of a document with a commit (if this
> works).
> > But I don't want any changes on the index, just start a new searcher
> > and close the old one. This is my problem. I don't see any X/Y here.
> >
> > Regards
> > Bernd
> >
> >
> > Am 15.07.2015 um 12:46 schrieb Alessandro Benedetti:
> > > Triggering a commit , implies the new Searcher to be opened in a soft
> > > commit scenario.
> > > With an hard commit, you can decide if opening or not the new searcher.
> > >
> > > But this is probably a X/Y problem.
> > >
> > > Can you describe better your real problem and not the way you were
> trying
> > > to solve it ?
> > >
> > > Cheers
> > >
> > > 2015-07-15 9:57 GMT+01:00 Andrea Gazzarini <a.gazzar...@gmail.com>:
> > >
> > >> On top of that sorry, I didn't answer to your question because I
> don't know
> > >> if that is possible
> > >>
> > >> Best,
> > >> Andrea
> > >> On 15 Jul 2015 02:51, "Andrea Gazzarini" <a.gazzar...@gmail.com>
> wrote:
> > >>
> > >>> What do you mean with "clean" state? A searcher is a view over a
> given
> > >>> index (let's say) "state"...if the state didn't change why do you
> want
> > >>> another (identical) view?
> > >>>
> > >>> On 15 Jul 2015 02:30, "Bernd Fehling" <
> bernd.fehl...@uni-bielefeld.de>
> > >>> wrote:
> > >>>>
> > >>>> I'm doing some testing on long running huge indexes.
> > >>>> Therefore I need a "clean" state after some days running.
> > >>>> My idea was to open a new searcher with commit command:
> > >>>>
> > >>>> INFO - org.apache.solr.update.DirectUpdateHandler2;
> > >>>> start
> > >>>
> > >>
> commit{,optimize=false,openSearcher=true,waitSearcher=true,expungeDeletes=false,softCommit=false,prepareCommit=false}
> > >>>> INFO - org.apache.solr.update.DirectUpdateHandler2; No uncommitted
> > >>> changes. Skipping IW.commit.
> > >>>> INFO - org.apache.solr.core.SolrCore; SolrIndexSearcher has not
> > >> changed
> > >>> - not re-opening: org.apache.solr.search.SolrIndexSearcher
> > >>>> INFO - org.apache.solr.update.DirectUpdateHandler2;
> end_commit_flush
> > >>>>
> > >>>> But the result is that the DirectUpdateHandler2 is skipping the
> > >> commit.
> > >>>>
> > >>>> Any other ideas how to force opening a new searcher without
> optimizing
> > >>> or loading anything?
> > >>>>
> > >>>> Best regards
> > >>>> Bernd
> > >>>
> > >>
> >
>
--
--------------------------
Benedetti Alessandro
Visiting card - http://about.me/alessandro_benedetti
Blog - http://alexbenedetti.blogspot.co.uk
"Tyger, tyger burning bright
In the forests of the night,
What immortal hand or eye
Could frame thy fearful symmetry?"
William Blake - Songs of Experience -1794 England
