lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Cao Manh Dat (JIRA)" <>
Subject [jira] [Commented] (SOLR-11458) Bugs in MoveReplicaCmd handling of failures
Date Thu, 30 Nov 2017 07:16:00 GMT


Cao Manh Dat commented on SOLR-11458:

This bug relates to HDFS lease recovery. When data dir of a replica (core_node7 in this case)
get deleted and get recovered when a new collection of the same name gets created. : for newly created core, should we skip lease recovery??

> Bugs in MoveReplicaCmd handling of failures
> -------------------------------------------
>                 Key: SOLR-11458
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>    Affects Versions: 7.0, 7.0.1, 7.1, master (8.0)
>            Reporter: Andrzej Bialecki 
>            Assignee: Andrzej Bialecki 
> Spin-off from SOLR-11449:
> {quote}
> There's a section of code in moveNormalReplica that ensures that we don't lose a shard
leader during move. There's no corresponding protection in moveHdfsReplica, which means that
moving a replica that is also a shard leader may potentially lead to data loss (eg. when replicationFactor=1).
> Also, there's no rollback strategy when moveHdfsReplica partially fails, unlike in moveNormalReplica
where the code simply skips deleting the original replica - it seems that the code should
attempt to restore the original replica in this case? When RF=1 and such failure occurs then
not restoring the original replica means lost shard.
> {quote}

This message was sent by Atlassian JIRA

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

View raw message