ChenSammi commented on PR #9362: URL: https://github.com/apache/ozone/pull/9362#issuecomment-3595410987
@rich7420 , thanks for working on this effort. IIUC, SCM doesn't track the new containers allocated with a specific DN, so in concurrent container allocation requests case, space check in SCM will pass while there is no enough space on DN to serve all new containers(DN side container allocation space reservation is now serialized(https://issues.apache.org/jira/browse/HDDS-12810), so DN will fail the requests when no enough space), so increase the available space requirement check from 5GB in SCM cannot guarantee solve the problem, since the concurrency is not a fixed status, it' hard to decide which number is enough in SCM. It's not a recommended way to introduce code complexity while it cannot guarantee solve the problem. -- 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]
