lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tim Vaillancourt <...@elementspace.com>
Subject Re: {soft}Commit and cache flusing
Date Tue, 08 Oct 2013 22:23:01 GMT
I have a genuine question with substance here. If anything this
nonconstructive, rude response was "to get noticed". Thanks for
contributing to the discussion.

Tim


On 8 October 2013 05:31, Dmitry Kan <solrexpert@gmail.com> wrote:

> Tim,
> I suggest you open a new thread and not reply to this one to get noticed.
> Dmitry
>
>
> On Mon, Oct 7, 2013 at 9:44 PM, Tim Vaillancourt <tim@elementspace.com
> >wrote:
>
> > Is there a way to make autoCommit only commit if there are pending
> changes,
> > ie: if there are 0 adds pending commit, don't autoCommit (open-a-searcher
> > and wipe the caches)?
> >
> > Cheers,
> >
> > Tim
> >
> >
> > On 2 October 2013 00:52, Dmitry Kan <solrexpert@gmail.com> wrote:
> >
> > > right. We've got the autoHard commit configured only atm. The
> > soft-commits
> > > are controlled on the client. It was just easier to implement the first
> > > version of our internal commit policy that will commit to all solr
> > > instances at once. This is where we have noticed the reported behavior.
> > >
> > >
> > > On Wed, Oct 2, 2013 at 9:32 AM, Bram Van Dam <bram.vandam@intix.eu>
> > wrote:
> > >
> > > > if there are no modifications to an index and a softCommit or
> > hardCommit
> > > >>>> issued, then solr flushes the cache.
> > > >>>>
> > > >>>
> > > > Indeed. The easiest way to work around this is by disabling auto
> > commits
> > > > and only commit when you have to.
> > > >
> > >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message