Sreeja created HDDS-15889:
-----------------------------
Summary: Report why container moves failed in iteration status
Key: HDDS-15889
URL: https://issues.apache.org/jira/browse/HDDS-15889
Project: Apache Ozone
Issue Type: Sub-task
Reporter: Sreeja
Assignee: Sreeja
When container moves fail during balancing, the only record is a WARN log entry
on the SCM leader:
Container move for container <id> from source <dn> to target <dn> failed:
<MoveResult>
MoveManager has 14 distinct {{MoveResult}} failure values
(REPLICATION_FAIL_INFLIGHT_REPLICATION, DELETE_FAIL_POLICY,
REPLICATION_NOT_HEALTHY_BEFORE_MOVE, DELETION_FAIL_NODE_UNHEALTHY, etc.), but
all of them are counted identically as numContainerMovesFailed in metrics and
shown as a single "Failed to move containers: N" line in ozone admin
containerbalancer status --verbose.
User who sees 5 failed moves cannot determine without manually grepping the SCM
log to know the reason.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
