clearing document cache || solr 6.6

[sachin gk <gk...@gmail.com>]

Hi All,

Is there a way to clear the *document cache* after we commit to the indexer.

-- 
Regards,
Sachin

Re: clearing document cache || solr 6.6

[Erick Erickson <er...@gmail.com>]

I'd also ask why you care? What benefit do you think you'd get
if you did explicitly flush the document cache?

You seem to think there's some benefit to programmatically
flushing the cache, but you haven't stated what that benefit is.

I suspect that you are making some assumptions that are not true
and that this is a waste of effort.

Best,
Erick

On Wed, Jan 30, 2019 at 9:46 AM Walter Underwood <wu...@wunderwood.org> wrote:
>
> You don’t need to do that. When there is a commit, Solr creates a new Searcher
> with an empty document cache.
>
> wunder
> Walter Underwood
> wunder@wunderwood.org
> http://observer.wunderwood.org/  (my blog)
>
> > On Jan 29, 2019, at 10:27 PM, sachin gk <gk...@gmail.com> wrote:
> >
> > Hi All,
> >
> > Is there a way to clear the *document cache* after we commit to the indexer.
> >
> > --
> > Regards,
> > Sachin
>

Re: clearing document cache || solr 6.6

[Walter Underwood <wu...@wunderwood.org>]

You don’t need to do that. When there is a commit, Solr creates a new Searcher
with an empty document cache.

wunder
Walter Underwood
wunder@wunderwood.org
http://observer.wunderwood.org/  (my blog)

> On Jan 29, 2019, at 10:27 PM, sachin gk <gk...@gmail.com> wrote:
> 
> Hi All,
> 
> Is there a way to clear the *document cache* after we commit to the indexer.
> 
> -- 
> Regards,
> Sachin

Re: clearing document cache || solr 6.6

[Shawn Heisey <ap...@elyograg.org>]

On 1/30/2019 2:27 AM, sachin gk wrote:
> To support an existing functionality we have turned the opensearcher to
> false. Is there a way to flush the cache programiticaly.

Executing a commit with openSearcher=true is the only way I know of 
without custom code.

When you commit with openSearcher set to false, it's generally much 
faster than with openSearcher set to true ... but any changes made to 
the index will not be visible to people making queries, because those 
will continue using the existing searcher that has no idea anything has 
changed.

If you're willing to write your own code, you can usually do just about 
anything you want.  There are no guarantees that what you want will 
actually be beneficial ... I agree with Erick on wondering why you would 
try to cripple Solr in this way.  Solr's caches are almost always a good 
thing when used appropriately.

Thanks,
Shawn

Re: clearing document cache || solr 6.6

[sachin gk <gk...@gmail.com>]

Thanks Shawn,

To support an existing functionality we have turned the opensearcher to
false. Is there a way to flush the cache programiticaly.

Regards,
Sachin

On Wed, Jan 30, 2019, 12:58 PM Shawn Heisey <apache@elyograg.org wrote:

> On 1/29/2019 11:27 PM, sachin gk wrote:
> > Is there a way to clear the *document cache* after we commit to the
> indexer.
>
> All Solr caches are invalidated when you issue a commit with
> openSearcher set to true.  The default setting is true, and normally it
> doesn't get set to false unless you explicitly set it.  Most of the
> time, autoCommit has openSearcher set to false.
>
> The documentCache cannot be warmed directly, but it does get items added
> to it if there are any warming queries, which may come from autowarming
> queryResultCache.
>
> Thanks,
> Shawn
>

Re: clearing document cache || solr 6.6

[Shawn Heisey <ap...@elyograg.org>]

On 1/29/2019 11:27 PM, sachin gk wrote:
> Is there a way to clear the *document cache* after we commit to the indexer.

All Solr caches are invalidated when you issue a commit with 
openSearcher set to true.  The default setting is true, and normally it 
doesn't get set to false unless you explicitly set it.  Most of the 
time, autoCommit has openSearcher set to false.

The documentCache cannot be warmed directly, but it does get items added 
to it if there are any warming queries, which may come from autowarming 
queryResultCache.

Thanks,
Shawn