hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tony Valderrama (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-1848) Datanodes should shutdown when a critical volume fails
Date Thu, 05 May 2011 16:33:03 GMT

     [ https://issues.apache.org/jira/browse/HDFS-1848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Tony Valderrama updated HDFS-1848:
----------------------------------

    Attachment: HDFS-1848.0-20-3-rc2.patch.1

Just as an example, this is how we implemented a feature similar to Eli's suggested part #1
on our internal 0.20-based branch.  This patch won't apply to 0.20.3, though, since it doesn't
include HDFS-457 et al.

> Datanodes should shutdown when a critical volume fails
> ------------------------------------------------------
>
>                 Key: HDFS-1848
>                 URL: https://issues.apache.org/jira/browse/HDFS-1848
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: data-node
>            Reporter: Eli Collins
>             Fix For: 0.23.0
>
>         Attachments: HDFS-1848.0-20-3-rc2.patch.1
>
>
> A DN should shutdown when a critical volume (eg the volume that hosts the OS, logs, pid,
tmp dir etc.) fails. The admin should be able to specify which volumes are critical, eg they
might specify the volume that lives on the boot disk. A failure in one of these volumes would
not be subject to the threshold (HDFS-1161) or result in host decommissioning (HDFS-1847)
as the decommissioning process would likely fail.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message