[
https://issues.apache.org/jira/browse/HDFS-8211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14509402#comment-14509402
]
Arpit Agarwal commented on HDFS-8211:
-------------------------------------
The storageUuid/storageId is different from the DatanodeUuid. The former is
allocated per storage directory. Yes it is confusing. :-)
I suggested using SimulatedFSDataSet so we can bypass this code block in
initStorage:
{code}
if (!factory.isSimulated()) {
final StartupOption startOpt = getStartupOption(conf);
...
{code}
Then all we'd need is a spy object for DataStorage which does nothing when
writeAll is invoked.
> 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: HDFS
> Affects Versions: 2.7.0
> Reporter: Anu Engineer
> Assignee: Anu Engineer
> Priority: Minor
> Attachments: hdfs-8211.001.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)
