Gargi-jais11 opened a new pull request, #285: URL: https://github.com/apache/ozone-site/pull/285
## What changes were proposed in this pull request? https://ozone-site-v2.staged.apache.org/docs/administrator-guide/operations/disk-replacement/datanodes A datanode may have multiple data volumes, specified in hdds.datanode.dir. For example, /data1,/data2,/data3 hdds.datanode.failed.data.volumes.tolerated: The number of data volumes that are allowed to fail before a datanode stops offering service. By default, this value is -1, meaning unlimited. Similarly, hdds.datanode.failed.metadata.volumes.tolerated allows a number of metadata volumes to fail. During datanode startup, it performs check to determine if a volume fails. If the datanode is allowed to continue without abort, the volume is taken off. After datanode starts, a periodic disk check is run every 60 minutes (determined by configuration property hdds.datanode.periodic.disk.check.interval.minutes. When a volume is determined failed, it is chosen by volume choosing policy to allocate new containers. To replace the failed disks, shut down the datanode, update hdds.datanode.dir to remove it from the directory list, and then restart the datanode. note: Ozone datanode does not support hotswap yet, meaning to update the disk list, it must restart the datanode process. The state of volumes can be seen in Datanode metrics and web UI. Also did some more add ons. ## What is the link to the Apache Jira? https://issues.apache.org/jira/browse/HDDS-14501 ## How was this patch tested? Check off which of the following tests were done on this change. If additional testing was done, please elaborate here as well. - [ ] The CI checks on my fork are passing - [ ] I verified the rendered content using a local preview - [ ] I manually verified the steps provided in this change work as described -- 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]
