Shuo Huang created HDDS-17763:
---------------------------------

             Summary: SCM pipeline limit includes failed metadata volumes
                 Key: HDDS-17763
                 URL: https://issues.apache.org/jira/browse/HDDS-17763
             Project: Apache Ozone
          Issue Type: Bug
            Reporter: Shuo Huang
            Assignee: Shuo Huang


When ozone.scm.datanode.pipeline.limit is set to 0, SCM calculates each 
datanode's pipeline limit from its metadata volume count.

Failed metadata volumes remain in the node report. 
DatanodeInfo#getMetaDataVolumeCount() counts them too, so a volume failure does 
not lower the calculated limit. SCM can keep selecting the datanode for new 
pipelines using the old limit.



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

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

Reply via email to