[ 
https://issues.apache.org/jira/browse/HDDS-13878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gargi Jaiswal updated HDDS-13878:
---------------------------------
    Summary: Cleanup   (was: Remove SCM part of DiskBalancer and update all 
Unit and Integration Tests)

> Cleanup 
> --------
>
>                 Key: HDDS-13878
>                 URL: https://issues.apache.org/jira/browse/HDDS-13878
>             Project: Apache Ozone
>          Issue Type: Sub-task
>            Reporter: Gargi Jaiswal
>            Assignee: Gargi Jaiswal
>            Priority: Major
>
> After implementing direct client-to-DN communication for DiskBalancer in 
> HDDS-13598, the SCM part is no longer needed and should be removed.
> *This JIRA covers:*
>  # Support *stdin* so that a list of datanodes can be easily passed in from a 
> file.
>  # Support *json* option to gather output from many nodes and just parse out 
> problematic ones.
>  # Remove the {*}-d/-{*}{*}-datanodes{*} flag and keep it as a list of space 
> separated arguments of datanodes similar to *ozone admin container info* .
>  # Additionally, configuration parameters should have corresponding long form 
> options like *--threshold* for clarity.
>  # Remove rest of the scm part connection with datanode
>  # Cleanup of obsolete protobuf definitions in 
> {color:#de350b}ScmServerDatanodeHeartbeatProtocol.proto{color} and 
> {color:#de350b}ScmAdminProtocol.proto{color}
>  # Rewriting integration tests ({color:#de350b}TestDiskBalancer, 
> TestDiskBalancerDuringDecommissionAndMaintenance{color}) for direct 
> communication
>  # Rewrite {color:#de350b}testdiskbalancer.robot {color}robot test.
>  # Do unit testing of all new diskbalancer subcommands.
>  # Update the design doc and feature doc for diskBalancer 
> ({color:#de350b}DiskBalancer.md{color}).
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to