hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Nauroth (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-7604) Track and display failed DataNode storage locations in NameNode.
Date Mon, 09 Feb 2015 22:04:36 GMT

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

Chris Nauroth updated HDFS-7604:
--------------------------------
    Attachment: HDFS-7604.002.patch

I'm attaching patch v002.  I've also attached screenshots 5-7 showing what it looks like in
the web UI now.

It's still very similar to the change summary I gave in one of my prior comments.  The differences
are:
* The UI now uses a separate page to track nodes with volume failures.  The existing DataNode
information page is unchanged.  On the Datanode Volume Failures page, you'll see only nodes
that currently have volume failures, and the details.
* The internal tracking and the heartbeat protocol now uses a {{VolumeFailureSummary}} message.
 This tracks more detailed information than the prior version, which was just a list of strings.

> Track and display failed DataNode storage locations in NameNode.
> ----------------------------------------------------------------
>
>                 Key: HDFS-7604
>                 URL: https://issues.apache.org/jira/browse/HDFS-7604
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: datanode, namenode
>            Reporter: Chris Nauroth
>            Assignee: Chris Nauroth
>         Attachments: HDFS-7604-screenshot-1.png, HDFS-7604-screenshot-2.png, HDFS-7604-screenshot-3.png,
HDFS-7604-screenshot-4.png, HDFS-7604-screenshot-5.png, HDFS-7604-screenshot-6.png, HDFS-7604-screenshot-7.png,
HDFS-7604.001.patch, HDFS-7604.002.patch, HDFS-7604.prototype.patch
>
>
> During heartbeats, the DataNode can report a list of its storage locations that have
been taken out of service due to failure (such as due to a bad disk or a permissions problem).
 The NameNode can track these failed storage locations and then report them in JMX and the
NameNode web UI.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message