ASF GitHub Bot logged work on HDDS-1982:

                Author: ASF GitHub Bot
            Created on: 11/Sep/19 17:38
            Start Date: 11/Sep/19 17:38
    Worklog Time Spent: 10m 
      Work Description: sodonnel commented on pull request #1344: HDDS-1982 
Extend SCMNodeManager to support decommission and maintenance states
URL: https://github.com/apache/hadoop/pull/1344#discussion_r323370846

 File path: 
 @@ -417,9 +451,12 @@ private SCMNodeStat getNodeStatInternal(DatanodeDetails 
datanodeDetails) {
   public Map<String, Integer> getNodeCount() {
+    // TODO - This does not consider decom, maint etc.
     Map<String, Integer> nodeCountMap = new HashMap<String, Integer>();
 Review comment:
   The existing code had Map<String, Integer>, but I agree it would be better 
with <NodeState, Integer> or <NodeStatus, Integer>. I plan to leave this as is 
for now, as this method is used only for JMX right now, and I plan to split 
that out into a separate change via HDDS-2113 as there are some open questions 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

Issue Time Tracking

    Worklog Id:     (was: 310884)
    Time Spent: 5h 40m  (was: 5.5h)

> Extend SCMNodeManager to support decommission and maintenance states
> --------------------------------------------------------------------
>                 Key: HDDS-1982
>                 URL: https://issues.apache.org/jira/browse/HDDS-1982
>             Project: Hadoop Distributed Data Store
>          Issue Type: Sub-task
>          Components: SCM
>            Reporter: Stephen O'Donnell
>            Assignee: Stephen O'Donnell
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 5h 40m
>  Remaining Estimate: 0h
> Currently, within SCM a node can have the following states:
> The last 2 are not currently used.
> In order to support decommissioning and maintenance mode, we need to extend 
> the set of states a node can have to include decommission and maintenance 
> states.
> It is also important to note that a node decommissioning or entering 
> maintenance can also be HEALTHY, STALE or go DEAD.
> Therefore in this Jira I propose we should model a node state with two 
> different sets of values. The first, is effectively the liveliness of the 
> node, with the following states. This is largely what is in place now:
> The second is the node operational state:
> That means the overall total number of states for a node is the cross-product 
> of the two above lists, however it probably makes sense to keep the two 
> states seperate internally.

This message was sent by Atlassian Jira

To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org

Reply via email to