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

ASF GitHub Bot logged work on HDDS-2196:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 14/Oct/19 09:42
            Start Date: 14/Oct/19 09:42
    Worklog Time Spent: 10m 
      Work Description: sodonnel commented on pull request #17: HDDS-2196 Add 
CLI Commands and Protobuf messages to trigger decom states
URL: https://github.com/apache/hadoop-ozone/pull/17
 
 
   This change provides 3 new CLI commands:
   
   ```
   scmcli dnadmin decommission hostname1 hostname2 hostname3
   scmcli dnadmin maintenance hostname1 hostname2 hostname3 < --end time from 
now to end maintenance in hours>
   scmcli dnadmin recommission hostname1 hostname2 hostname3
   ```
   
   To allow for cases where many DNs are on the same host, the hostname can 
also have a port appended, eg:
   
   ```
   scmcli dnadmin decommission hostname1:5678 hostname1:6789 hostname1:7890
   ```
   
   These commands make use of 3 new protobuf messages, defined in 
StorageContainerLocationProtocol:
   
   ```
   DecommissionNodesRequestProto + DecommissionNodesResponseProto
   RecommissionNodesRequestProto + RecommissionNodesResponseProto
   StartMaintenanceNodesRequestProto + StartMaintenanceNodesResponseProto
   ```
   
   All 3 accept a list of strings (for hostnames) and the maintenance message 
also allows an int to specify the end time in hours.
   
   These 3 commands make a call to a new class NodeDecommissionManager which 
takes the list of hosts and validates them. If any host is invalid or not part 
of the cluster, the entire command is failed and the CLI will show an error. 
Assuming the validation passes OK, the list of nodes will be switch into 
DECOMMISSIONING, ENTERING_MAINTENANCE or back into IN_SERVICE.
   
   At this point in time, there is no decommission logic present, the nodes 
will simply remain in the interm state forever. The actual decommissioning 
logic will be added in a further Jira.
 
----------------------------------------------------------------
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:
us...@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 327699)
    Time Spent: 50m  (was: 40m)

> Add CLI Commands and Protobuf messages to trigger decom states
> --------------------------------------------------------------
>
>                 Key: HDDS-2196
>                 URL: https://issues.apache.org/jira/browse/HDDS-2196
>             Project: Hadoop Distributed Data Store
>          Issue Type: Sub-task
>          Components: SCM, SCM Client
>    Affects Versions: 0.5.0
>            Reporter: Stephen O'Donnell
>            Assignee: Stephen O'Donnell
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> To all nodes to be decommissioned, recommissioned and put into maintenance, 
> we need a few commands.
> These will be added to the existing "scm cli". 3 commands are proposed:
> Decommission:
> ozone scmcli dnadmin decommission hosta hostb hostc:port ...
> Put nodes into maintenance:
> osone scmcli dnadmin maintenance hosta hostb hostc:port ... <-endHours>
> Take nodes out of maintenance or halt decommission:
> ozone scmcli dnadmin recommission hosta hostb hostc:port
> These 3 commands will call 3 new protobuf messages and they will be part of 
> the "StorageContainerLocationProtocol":
>  * DecommissionNodesRequestProto
>  * RecommissionNodesRequestProto
>  * StartMaintenanceNodesRequestProto
> In additional a new class NodeDecommissionManager will be introduced that 
> will receive these commands and carry out the decommission steps.
> In this patch NodeDecommissionManager is only a skeleton implementation to 
> receive the commands as this patch is mainly focused on getting the CLI 
> commands and protobuf messages in place.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
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