ChenSammi commented on PR #7927:
URL: https://github.com/apache/ozone/pull/7927#issuecomment-2673908021

   One thing I just thought about is, with this new change, if user has ever 
set the "hdds.datanode.dir.du.reserved" or 
"hdds.datanode.dir.du.reserved.percent", for those non ozone services, will be 
too much from reservation point of view after Ozone version upgrade. For 
example, If Ozone DN is co-deployed with YARN service, which need disk space 
for shuffle data and all other data. User may set the 
"hdds.datanode.dir.du.reserved.percent" to 20% or 30%. Then it will be too much 
for this new calculation logic. 


-- 
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]

Reply via email to