Hi Alex, Hi All,

So. I'm a bit at a lost here.

For my given collection, I have both soft and hard commits. First every 15
seconds, 2nd every 60 seconds. My collection has 2 shards, each without any
replica. So I don't think the index replication is involved, right? We
pushed some data into this collection last night, and  this morning, hours
after, "Current" still shows red... Is there any way I can
debug/investigate/troubleshoot that?

Thanks,

JMS


Le mer. 19 sept. 2018 à 16:46, Jean-Marc Spaggiari <jean-m...@spaggiari.org>
a écrit :

> Hi Alex,
>
> Thanks for replying.
>
> I also found this:
> http://mail-archives.apache.org/mod_mbox/lucene-solr-user/201404.mbox/%3c53483062.2000...@elyograg.org%3E
> where it says "s basically means that Lucene has detected an index state
> where something has made changes to the index, but those changes are not
> yet visible.  To make them visible and return this status to 'true', do a
>  commit or soft commit with openSearcher enabled."
>
> That is interesting because my "current" flag almost never turns green,
> and indeed my openSearcher is disabled... So I'm a bit lost about what it
> should be ad if having "current" always red is really an issue or not... :-/
>
> JMS
>
> Le mer. 19 sept. 2018 à 14:44, Alexandre Rafalovitch <arafa...@gmail.com>
> a écrit :
>
>> I would say this is the relevant page for the "current" and
>> "generation"
>> https://lucene.apache.org/solr/guide/6_6/index-replication.html
>>
>> And I think generation refers to the actual Lucene index, so is
>> explained further here:
>>
>> https://lucene.apache.org/core/6_6_0/core/org/apache/lucene/codecs/lucene62/package-summary.html#package.description
>>
>> Regards,
>>    Alex.
>>
>> On 19 September 2018 at 14:33, Jean-Marc Spaggiari
>> <jean-m...@spaggiari.org> wrote:
>> > Hi dear SOLR community.
>> >
>> > On this page of the documentation:
>> > https://lucene.apache.org/solr/guide/6_6/core-specific-tools.html what
>> are
>> > the fields "current" and "gen" referring to? I have not been able to
>> find
>> > that anywhere :(
>> >
>> > Thanks,
>> >
>> > JMS
>>
>

Reply via email to