vtutrinov opened a new pull request, #5721: URL: https://github.com/apache/ozone/pull/5721
## What changes were proposed in this pull request? The algorithm of detection of the datanode availability for a new container was different between the SCM and datanodes in case of EC buckets. The SCM doesn't take into account the committed bytes count and serves the client with an invalid pipeline and then the datanodes from the provided pipeline will fail to create new containers The PR proposes a common way of computing the datanode availability for a new container allocation ## What is the link to the Apache JIRA https://issues.apache.org/jira/browse/HDDS-9807 ## How was this patch tested? * manually in a way described in the jira ticket, * new unit test that checks the datanode is not available to allocate a new container in case of increasing committed bytes count -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
