hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (Jira)" <j...@apache.org>
Subject [jira] [Work logged] (HDDS-1982) Extend SCMNodeManager to support decommission and maintenance states
Date Fri, 23 Aug 2019 16:19:00 GMT

     [ https://issues.apache.org/jira/browse/HDDS-1982?focusedWorklogId=300358&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-300358

ASF GitHub Bot logged work on HDDS-1982:

                Author: ASF GitHub Bot
            Created on: 23/Aug/19 16:18
            Start Date: 23/Aug/19 16:18
    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
   Remove the existing decommission states from the protobuf definition.
   At this stage, this PR is really a test to see if the build passes with these states removed.
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: 300358)
    Remaining Estimate: 0h
            Time Spent: 10m

> 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: 10m
>  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-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org

View raw message