[jira] [Created] (HDDS-10198) Improve Logging in AbstractFindTargetGreedy

["Siddhant Sangwan (Jira)" <ji...@apache.org>]

Siddhant Sangwan created HDDS-10198:
---------------------------------------

             Summary: Improve Logging in AbstractFindTargetGreedy
                 Key: HDDS-10198
                 URL: https://issues.apache.org/jira/browse/HDDS-10198
             Project: Apache Ozone
          Issue Type: Bug
          Components: SCM
    Affects Versions: 1.4.0
            Reporter: Siddhant Sangwan
            Assignee: Siddhant Sangwan


This jira is to improve logging around a Datanode being removed from the collection of potential targets in ContainerBalancer. This can help us understand why a particular Datanode wasn't chosen as a target for container move when we think it's the optimal choice. 

A Datanode may not be selected in multiple situations - it has already had enough size moved into it and has reached the limit, doesn't follow placement policy, already has the container's replica etc. I saw a situation in which a particular Datanode was the best choice when considering network distance and was also a potential target, but balancer did not choose it. I want to debug why this happened and more logging will help with this.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org