lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Markus Jelsma (JIRA)" <>
Subject [jira] [Commented] (SOLR-4260) Inconsistent numDocs between leader and replica
Date Thu, 18 Jul 2013 13:12:49 GMT


Markus Jelsma commented on SOLR-4260:

FYI: we're still seeing major inconsistencies, facet counts are off and when inspecting leaders
and replica's we notice not all are in sync. This is on yesterday's trunk and with an empty
index. There were no node failures during indexing. Shard_b's stats for example:

node 2 shard b
Last Modified:    about a minute ago
Num Docs:    158964
Max Doc:    158964
Deleted Docs:    0
Version:    4479
Segment Count:    1

node 3 shard b
Last Modified:    2 minutes ago
Num Docs:    158298
Max Doc:    158298
Deleted Docs:    0
Version:    2886

Size and versions are also different. Cluster is optimized/forceMerged but doesn't change
the facts as expected. At least one other shard also has differences in its two replica's,
i haven't manually checked the others.
> Inconsistent numDocs between leader and replica
> -----------------------------------------------
>                 Key: SOLR-4260
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>          Components: SolrCloud
>    Affects Versions: 5.0
>         Environment:
>            Reporter: Markus Jelsma
>            Priority: Critical
>             Fix For: 5.0
> After wiping all cores and reindexing some 3.3 million docs from Nutch using CloudSolrServer
we see inconsistencies between the leader and replica for some shards.
> Each core hold about 3.3k documents. For some reason 5 out of 10 shards have a small
deviation in then number of documents. The leader and slave deviate for roughly 10-20 documents,
not more.
> Results hopping ranks in the result set for identical queries got my attention, there
were small IDF differences for exactly the same record causing a record to shift positions
in the result set. During those tests no records were indexed. Consecutive catch all queries
also return different number of numDocs.
> We're running a 10 node test cluster with 10 shards and a replication factor of two and
frequently reindex using a fresh build from trunk. I've not seen this issue for quite some
time until a few days ago.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message