[
https://issues.apache.org/jira/browse/HDDS-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16553897#comment-16553897
]
Hudson commented on HDDS-262:
-----------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #14622 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/14622/])
HDDS-262. Send SCM healthy and failed volumes in the heartbeat. (nanda: rev
16f9aee5f55bc37c1bb243708ee9b3f97e5a5b83)
* (edit)
hadoop-hdds/container-service/src/main/java/org/apache/hadoop/ozone/container/common/volume/HddsVolume.java
* (edit)
hadoop-hdds/container-service/src/test/java/org/apache/hadoop/ozone/container/common/volume/TestVolumeSet.java
* (edit)
hadoop-hdds/container-service/src/main/java/org/apache/hadoop/ozone/container/common/volume/VolumeSet.java
> Send SCM healthy and failed volumes in the heartbeat
> ----------------------------------------------------
>
> Key: HDDS-262
> URL: https://issues.apache.org/jira/browse/HDDS-262
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Reporter: Bharat Viswanadham
> Assignee: Bharat Viswanadham
> Priority: Major
> Fix For: 0.2.1
>
> Attachments: HDDS-262.00.patch, HDDS-262.01.patch, HDDS-262.02.patch,
> HDDS-262.03.patch, HDDS-262.04.patch
>
>
> The current code only sends volumes which are successfully created during
> datanode startup. For any volume an error occurred during HddsVolume object
> creation, we should move that volume to failedVolume Map. This should be sent
> to SCM as part of NodeReports.
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
