ChenSammi commented on PR #7927: URL: https://github.com/apache/ozone/pull/7927#issuecomment-2684395158
@symious , current we have 1. `hdds.datanode.dir.du.reserved` and `hdds.datanode.dir.du.reserved.percent`, similar properties inherited from HDFS, which defines the space left for non-Ozone use. 2. `hdds.datanode.volume.min.free.space` and `hdds.datanode.volume.min.free.space.percent`, introduced in [HDDS-8254](https://issues.apache.org/jira/browse/HDDS-8254), which defines that if the volume free space reaches this value, volume will be treated as full. I totally agree it's a good idea. Based the current state, I would propose instead of change `hdds.datanode.dir.du.reserved` and `hdds.datanode.dir.du.reserved.percent` concepts, reuse `hdds.datanode.volume.min.free.space` and `hdds.datanode.volume.min.free.space.percent`. Make the SCM pipeline allocation, container allocation, container candidate selection in container balancer, container selection in replication manager, all aware of this min.free.space, so that disk full. can be avoided. What do you think @symious? cc @sadanand48, @vtutrinov . -- 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]
