jojochuang opened a new pull request, #8585:
URL: https://github.com/apache/ozone/pull/8585

   ## What changes were proposed in this pull request?
   HDDS-13208. [Docs] Add volume management section under 
Architecture/Datanodes.
   
   Please describe your PR in detail:
   * Draft was generated by Copilot Agent (Preview) using prompt:
   ```
   I tried to find any reference to volumes in an Ozone Datanode, but couldn't 
find any.
   
   https://ozone.apache.org/docs/edge/concept/datanodes.html
   
   I want to add a section "Volume management" in Datanodes.md
   
   We should
   (1) explain what a volume is in the context of Ozone DataNode; do not 
confuse it with namespace volumes in Ozone Manager. That a "volume" is 
essentially a disk, and a volume stores many containers.
   (2) I wanted to also add descriptions for volume choosing policy. Find the 
description for the property hdds.datanode.volume.choosing.policy. There are 
two policies: CapacityVolumeChoosingPolicy (default) and 
RoundRobinVolumeChoosingPolicy. Use the source code as the source of truth to 
explain what they do and how they work.
   (3) Create a table to include configuration properties related to volumes. 
Include default values and descriptions.
   (3) Add a disk balancer description – while volume choosing policy is 
useful, cluster operations can result in imbalanced disks. For example, in 
scenarios that we need to add new disks or to replace broken disks, the 
datanode's disks usage becomes uneven Ozone community is developing a new 
feature 'disk balancer' that aims to balance disks of Datanodes. The feature is 
under development of 
[HDDS-5713](https://issues.apache.org/jira/browse/HDDS-5713), and is coming 
soon.
   ```
   
   ## What is the link to the Apache JIRA
   
   https://issues.apache.org/jira/browse/HDDS-13208
   
   ## How was this patch tested?
   
   User doc


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