[
https://issues.apache.org/jira/browse/SOLR-12433?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cao Manh Dat updated SOLR-12433:
--------------------------------
Summary: Recovering flag of a replica is set equals to leader even it
failed to receive update on recovering (was: Raft term of a replica is set
equals to leader even it failed to receive update on recovering)
> Recovering flag of a replica is set equals to leader even it failed to
> receive update on recovering
> ---------------------------------------------------------------------------------------------------
>
> Key: SOLR-12433
> URL: https://issues.apache.org/jira/browse/SOLR-12433
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Cao Manh Dat
> Assignee: Cao Manh Dat
> Priority: Major
>
> When digging into RestartWhileUpdatingTest failure, I see that term of
> replicas is kinda mess up.
> {quote}
> [junit4] 1> /collections/collection1/terms/shard1 (0)
> [junit4] 1> DATA:
> [junit4] 1> {
> [junit4] 1> "core_node24_recovering":4,
> [junit4] 1> "core_node22":4,
> [junit4] 1> "core_node26_recovering":4,
> [junit4] 1> "core_node24":2,
> [junit4] 1> "core_node26":3}
> {quote}
> By design, the {{core_node24_recovering}} and {{core_node24}} should be
> always equals to each other. The reason here is
> {{ZkShardTerms.ensureTermsIsHigher}} also increase the
> {{core_node24_recovering}} is a higher number. This will lead to a case when
> a replica finished recovering but it won't be able to become active.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
