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.
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
>>>
>>
