[
https://issues.apache.org/jira/browse/SOLR-5309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14045041#comment-14045041
]
Shalin Shekhar Mangar edited comment on SOLR-5309 at 6/26/14 7:21 PM:
----------------------------------------------------------------------
I found the problem. There was a failure in adding doc id=219 because of
ongoing shard state transition.
grepping for '\{add=\[219' on the logs gives:
{code}
[junit4] 2> 549812 T2538 C532 P35504 oasup.LogUpdateProcessor.finish
[collection1] webapp= path=/update params={wt=javabin&version=2&CONTROL=TRUE}
{add=[219 (1471974763729518592)]} 0 1
{code}
So id=219 was added only on the "control" collection.
However, the same document was selected for deletion later. Grepping for
'\{delete=\[219' gives:
{code}
[junit4] 2> 570348 T2541 C532 P35504 oasup.LogUpdateProcessor.finish
[collection1] webapp= path=/update params={wt=javabin&version=2} {delete=[219
(-1471974785263075328)]} 0 0
[junit4] 2> 570352 T2540 C538 P35504 oasup.LogUpdateProcessor.finish
[collection1_shard1_0_replica2] webapp= path=/update
params={update.distrib=FROMLEADER&distrib.from=http://127.0.0.1:49012/collection1_shard1_0_replica1/&wt=javabi
n&version=2} {delete=[219 (-1471974785265172480)]} 0 1
[junit4] 2> 570352 T2580 C537 P49012 oasup.LogUpdateProcessor.finish
[collection1_shard1_0_replica1] webapp= path=/update
params={wt=javabin&version=2} {delete=[219 (-1471974785265172480)]} 0 2
{code}
Of course, since id=219 was never added in the first place, then its deletion
doesn't change the doc counts. The fix is make sure that docs which couldn't be
added are not considered for deletion. This is a bug in the test.
was (Author: shalinmangar):
I found the problem. There was a failure in adding doc id=219 because of
ongoing shard state transition.
grepping for '\{add=\[219' on the logs gives:
{code}
[junit4] 2> 549812 T2538 C532 P35504 oasup.LogUpdateProcessor.finish
[collection1] webapp= path=/update params={wt=javabin&version=2&CONTROL=TRUE}
{add=[219 (1471974763729518592)]} 0 1
{code}
So id=219 was added only on the "control" collection.
However, the same document was selected for deletion later. Grepping for
'\{delete=\[219' gives:
{code}
[junit4] 2> 570348 T2541 C532 P35504 oasup.LogUpdateProcessor.finish
[collection1] webapp= path=/update params={wt=javabin&version=2} {delete=[219
(-1471974785263075328)]} 0 0
[junit4] 2> 570352 T2540 C538 P35504 oasup.LogUpdateProcessor.finish
[collection1_shard1_0_replica2] webapp= path=/update
params={update.distrib=FROMLEADER&distrib.from=http://127.0.0.1:49012/collection1_shard1_0_replica1/&wt=javabi
n&version=2} {delete=[219 (-1471974785265172480)]} 0 1
[junit4] 2> 570352 T2580 C537 P49012 oasup.LogUpdateProcessor.finish
[collection1_shard1_0_replica1] webapp= path=/update
params={wt=javabin&version=2} {delete=[219 (-1471974785265172480)]} 0 2
{code}
Of course, since id=219 was never added in the first place, then its deletion
doesn't change the doc counts. The fix is make sure that docs which couldn't be
added are not considered for deletion.
> Investigate ShardSplitTest failures
> -----------------------------------
>
> Key: SOLR-5309
> URL: https://issues.apache.org/jira/browse/SOLR-5309
> Project: Solr
> Issue Type: Task
> Components: SolrCloud
> Reporter: Shalin Shekhar Mangar
> Assignee: Shalin Shekhar Mangar
> Priority: Blocker
>
> Investigate why ShardSplitTest if failing sporadically.
> Some recent failures:
> http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Windows/3328/
> http://jenkins.thetaphi.de/job/Lucene-Solr-trunk-Linux/7760/
> http://jenkins.thetaphi.de/job/Lucene-Solr-4.x-MacOSX/861/
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
