Omkar Dhayagude created HDDS-11772:
--------------------------------------
Summary: Ozone Used Capacity shown in Recon is not matching with
the input data size
Key: HDDS-11772
URL: https://issues.apache.org/jira/browse/HDDS-11772
Project: Apache Ozone
Issue Type: Bug
Components: Ozone Recon
Reporter: Omkar Dhayagude
*Steps to reproduce issue:*
1. Create a CDP 7.3.1 YCloud cluster
2. Go Ozone Recon & note down the original Cluster Capacity and number of keys,
buckets & volumes.
Hover over Cluster Capacity bar to see more details & note Ozone Used space.
3. The values are:
* Cluster Capacity = ~984.4 GB
* Ozone used = 1.7 GB
* Volumes = 1 | Buckets = 1 | Keys = 0
4. From CLI start a freon workload for 15 mins to load data of size 100 MB
5. After 15 mins i.e. after finishing the WL and considering replication factor
(RF = 3), disk space consumed for Ozone is 307200000 bytes = 300 MB.
6. Now go to Recon web UI & observe the previously noted parameters again.
7. Also check the volume/bucket/keys size from Recon > Disk Usage
*Observed results:*
1. The values are:
* Cluster Capacity = ~1 TB
* Ozone used = 56.5 GB
* Volumes = 2 | Buckets = 2 | Keys = 1000
* Disk Usage: vol1/bucket1 = 97.7 MB
Here, the ozone used space is increased from 1.7 GB to 56.5 GB, where we loaded
only ~ 300 MB.
2. The before & after values have irrelevant difference and are inconsistent
mathematically.
*Expected result:*
Ozone used capacity in Recon should match according to the input data loaded.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
