You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Eli Collins (JIRA)" <ji...@apache.org> on 2010/05/11 07:57:31 UTC

[jira] Commented: (HDFS-811) Additional tests(Unit tests & Functional tests) for HDFS-457.

    [ https://issues.apache.org/jira/browse/HDFS-811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12866067#action_12866067 ] 

Eli Collins commented on HDFS-811:
----------------------------------

The automated test covers the following but I also verified by hand on a local cluster that:
# Making a datadir inaccessible causes the volume to be blacklisted, the capacities and failed volume count adjusted accordingly on the web UI stats (using HDFS-556). 
# Making the datadir accessible again does not cause it to be used until the datanode is restarted, at which point the failed volume count and capacities are back to their original values
# The above but made *all* datadirs inaccessible, confirmed the datanode is not used and is eventually is reported as dead.



> Additional tests(Unit tests & Functional tests)  for HDFS-457.
> --------------------------------------------------------------
>
>                 Key: HDFS-811
>                 URL: https://issues.apache.org/jira/browse/HDFS-811
>             Project: Hadoop HDFS
>          Issue Type: Test
>          Components: test
>    Affects Versions: 0.22.0
>            Reporter: Ravi Phulari
>            Assignee: Eli Collins
>            Priority: Minor
>             Fix For: 0.22.0
>
>         Attachments: hdfs-811-1.patch
>
>
>  HDFS-457 introduced a improvement which allows  datanode to continue if a volume for replica storage fails. Previously a datanode resigned if any volume failed. 
> Description of HDFS-457
> {quote}
> Current implementation shuts DataNode down completely when one of the configured volumes of the storage fails.
> This is rather wasteful behavior because it decreases utilization (good storage becomes unavailable) and imposes extra load on the system (replication of the blocks from the good volumes). These problems will become even more prominent when we move to mixed (heterogeneous) clusters with many more volumes per Data Node.
> {quote}
> I suggest following additional tests for this improvement. 
> #1 Test successive  volume failures ( Minimum 4 volumes )
> #2 Test if each volume failure reports reduction in available DFS space and remaining space.
> #3 Test if failure of all volumes on a data nodes leads to the data node failure.
> #4 Test if correcting failed storage disk brings updates and increments available DFS space. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.