sadanand48 commented on PR #4583: URL: https://github.com/apache/ozone/pull/4583#issuecomment-1521222284
Thanks @sumitagrawl for the review, I have now aligned the config to take effect even during container allocation on a volume during its creation. So the flow would be 1. Volume reaches this threshold usage ratio 2. Any further writes on these containers would cause the DN to send container action to the SCM. 3. SCM would receive the action and close these containers. 4. New client writes will trigger container creation and the VolumeChoosingPolicy would make sure that these volumes are not selected and check this property there too. This way the problem of small containers getting created is eliminated. > client may face failure of closed container On client retry new containers should be allocated in this case. -- 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]
