[
https://issues.apache.org/jira/browse/HDDS-13054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sammi Chen updated HDDS-13054:
------------------------------
Fix Version/s: 2.1.0
Resolution: Fixed
Status: Resolved (was: Patch Available)
> [DiskBalancer] Stop DiskBalancer when DN enters DECOMMISSIONING or
> MAINTENANCE states
> -------------------------------------------------------------------------------------
>
> Key: HDDS-13054
> URL: https://issues.apache.org/jira/browse/HDDS-13054
> Project: Apache Ozone
> Issue Type: Sub-task
> Reporter: Gargi Jaiswal
> Assignee: Gargi Jaiswal
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.1.0
>
>
> When DN enters in *{{DECOMMISSIONING}}* or *{{MAINTENANCE}}* states,
> DiskBalancer on that DN should be stopped and resume again after DN turns to
> normal state. This needs to be fixed.
> This JIRA will also tracks the addition of integration tests to validate
> DiskBalancer's behaviour when a DataNode (DN) transitions into
> *{{DECOMMISSIONING}}* or *{{MAINTENANCE}}* states.
> *Test Scenarios:* When DiskBalancer is running mark one DN as Decommissioned
> and other as Maintenance.
> *Setup:* Create a cluster with 5 DNs, each having multiple data volumes.
> *Description:* Start DiskBalancer on all DNs. While it's actively balancing,
> decommission one of the DNs and mark other DN state as Maintenance.
> *Expected Behaviour:*
> * Disk balancer should pause itself if the DN state is maintenance or
> decomissioning, decomissioned.
> * DN status marked as STOPPED and should not include the decommissioned
> DataNode in the output of diskbalancer status and report.
> * Other active DataNodes should continue balancing without disruption.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
