siddhantsangwan commented on PR #5758: URL: https://github.com/apache/ozone/pull/5758#issuecomment-1882817331
Ah, I understand. Yes, I've seen this happen in some small clusters. The recommendation is to increase the value of `datanodes.involved.max.percentage.per.iteration` accordingly. For example, it can be set to 100 for clusters of 15 Datanodes or less so that all Datanodes may be involved in balancing. Do you have any reason to not do this and make a code change instead? It doesn't make sense to have a configuration `datanodes.involved.max.percentage.per.iteration` which imposes a limit, and then have another configuration `adapt.balance.when.reach.the.limit` which will effectively disable the former limit. Why not just change `datanodes.involved.max.percentage.per.iteration`? -- 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]
