smengcl commented on code in PR #8365: URL: https://github.com/apache/ozone/pull/8365#discussion_r2069840812
########## hadoop-hdds/docs/content/design/dn-usedspace-calculation.md: ########## @@ -0,0 +1,87 @@ +--- +title: Datanode used space calculation +summary: Describe proposal for optimization in datanode used space calculation. +date: 2025-04-30 +jira: HDDS-12924 +status: draft +author: Sumit Agrawal +--- +<!-- + Licensed under the Apache License, Version 2.0 (the "License"); + you may not use this file except in compliance with the License. + You may obtain a copy of the License at + http://www.apache.org/licenses/LICENSE-2.0 + Unless required by applicable law or agreed to in writing, software + distributed under the License is distributed on an "AS IS" BASIS, + WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. + See the License for the specific language governing permissions and + limitations under the License. See accompanying LICENSE file. +--> + +# Abstract +Datanode makes use of DU to identify disk space uses for ozone in the volume. +DU is a time-consuming operation if run over large occupied disk, like when running over disk path having 10s of TB container data. This will be slow operation. + + +## Approach 1: Run DU over non-ozone path + +Challenges: + +- Root path is not known for the device mounted on. So this needs extra configuration. +- Permission problem: du will not count the space if permission is not there on a certain path. + + +Based on the above concern, it's `not feasible` to do du over non-ozone path. Review Comment: Thoughts? @errose28 -- 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]
