[
https://issues.apache.org/jira/browse/SOLR-4260?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13874434#comment-13874434
]
Shawn Heisey commented on SOLR-4260:
------------------------------------
This might be old news by now, but I noticed it while updating my test system,
so I'm reporting it.
The lucene_solr_4_6 branch fails to compile with these fixes committed. One of
the changes removes the import for RemoteSolrException from SolrCmdDistributor,
but the doRetries method still uses this exception. That method is very
different in 4.6 than it is in branch_4x. Everything's good on branch_4x.
Re-adding the import fixes the problem, but the discrepancy between the two
branches needs some investigation.
The specific code that fails to compile with the removed import seems to have
been initially added to trunk by revision 1545464 (2013/11/25) and removed from
trunk by revision 1546670 (2013/11/29). It was then re-added to
lucene_solr_4_6 by revision 1554122 (2013/12/29).
> Inconsistent numDocs between leader and replica
> -----------------------------------------------
>
> Key: SOLR-4260
> URL: https://issues.apache.org/jira/browse/SOLR-4260
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Environment: 5.0.0.2013.01.04.15.31.51
> Reporter: Markus Jelsma
> Assignee: Mark Miller
> Priority: Critical
> Fix For: 5.0, 4.7, 4.6.1
>
> Attachments: 192.168.20.102-replica1.png,
> 192.168.20.104-replica2.png, SOLR-4260.patch, clusterstate.png,
> demo_shard1_replicas_out_of_sync.tgz
>
>
> 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 was sent by Atlassian JIRA
(v6.1.5#6160)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
