[ https://issues.apache.org/jira/browse/HDFS-12887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16277739#comment-16277739 ]
Virajith Jalaparti commented on HDFS-12887: ------------------------------------------- This fix ensures that Datanodes can start successfully in the following scenario: # Datanode DN1 is configured with {{PROVIDED}} and {{DISK}} volumes. # Increase in replication on a (provided) file containing block {{i}} leads to DN1 moving block {{i}} from {{PROVIDED}} volume to the {{DISK}} volume. # DN1 goes down. # DN1 starts up, and finds block with id {{i}} on both the {{DISK}} and {{PROVIDED}} volumes and *fails to start* ({{IOException}} is thrown in {{ProvidedBlockPoolSlice.fetchVolumeMap}}). This scenario can be avoided once HDFS-9810 is completed. > [READ] Allow Datanodes with Provided volumes to start when blocks with the > same id exist locally > ------------------------------------------------------------------------------------------------ > > Key: HDFS-12887 > URL: https://issues.apache.org/jira/browse/HDFS-12887 > Project: Hadoop HDFS > Issue Type: Sub-task > Reporter: Virajith Jalaparti > Assignee: Virajith Jalaparti > > Fix {{ProvidedVolumeImpl.getVolumeMap}} to not throw an exception even when > an existing block in the volumemap has the same id. -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org