[
https://issues.apache.org/jira/browse/HDFS-8211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Walter Su updated HDFS-8211:
----------------------------
Priority: Major (was: Minor)
Changes Priority to Major.
As [~qwertymaniac] pointed out, this patch unintentionally fixes an issue that
DN may regenerate its UUIDs unintentionally (See HDFS-9949).
I think we should backport this to branch-2.7 ??
> DataNode UUID is always null in the JMX counter
> -----------------------------------------------
>
> Key: HDFS-8211
> URL: https://issues.apache.org/jira/browse/HDFS-8211
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: datanode
> Affects Versions: 2.7.0
> Reporter: Anu Engineer
> Assignee: Anu Engineer
> Fix For: 2.8.0
>
> Attachments: hdfs-8211.001.patch, hdfs-8211.002.patch
>
>
> The DataNode JMX counters are tagged with DataNode UUID, but it always gets a
> null value instead of the UUID.
> {code}
> Hadoop:service=DataNode,name=FSDatasetState*-null*.
> {code}
> This null is supposed be the datanode UUID.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
