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

   ## What changes were proposed in this pull request?
   
   Please see the jira for the problem description. 
   
   Changes proposed:
   1. In Datanode storage reports, also include raw file system stats: 
Filesystem Capacity, Filesystem Available. These are different from the current 
capacity and available space that's reported.
   
   `capacity = fsCapacity - du.reserved`
   
   This is what the new proto message looks like:
   ```
   message StorageReportProto {
     required string storageUuid = 1;
     required string storageLocation = 2;
     optional uint64 capacity = 3 [default = 0];
     optional uint64 scmUsed = 4 [default = 0];
     optional uint64 remaining = 5 [default = 0];
     optional StorageTypeProto storageType = 6 [default = DISK];
     optional bool failed = 7 [default = false];
     optional uint64 committed = 8 [default = 0];
     optional uint64 freeSpaceToSpare = 9 [default = 0];
     optional uint64 reserved = 10;
     /*
      Raw filesystem stats (as reported by the local filesystem). These 
represent the real device
      capacity/available, independent of Ozone's reserved-space adjustment.
      */
     optional uint64 fsCapacity = 11 [default = 0];
     optional uint64 fsAvailable = 12 [default = 0];
   }
   ```
   
   Note `fsUsed` is not reported in the heartbeat as it can be calculated where 
needed using `fsCapacity - fsAvailable`.
   
   2. These stats are then updated at various places: Datanode metrics, SCM 
metrics, usageinfo command, and Recon Datanodes page mouse hover screen.
   3. The Recon main overview page is not updated in this PR - that can be done 
in a separate PR.
   
   ## What is the link to the Apache JIRA
   
   https://issues.apache.org/jira/browse/HDDS-14446
   
   ## How was this patch tested?
   
   Edited and added various unit tests. Will also attach UI screenshots in some 
time.
   
   PR is draft while CI runs in my fork.
   


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