[ 
https://issues.apache.org/jira/browse/HDDS-11987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17910055#comment-17910055
 ] 

Devesh Kumar Singh commented on HDDS-11987:
-------------------------------------------

Recon is computing quota and setting only 2 fields in QuotaResponse : {*}Quota 
Allowed ({*}refer 
[this|https://github.com/apache/ozone/blob/8f2689dfe5f9b79e64f7d78acbaaf300c1ccbd1c/hadoop-ozone/recon/src/main/java/org/apache/hadoop/ozone/recon/api/handlers/VolumeEntityHandler.java#L167]{*}){*}
 and {*}Quota Used ({*}refer 
[this|https://github.com/apache/ozone/blob/8f2689dfe5f9b79e64f7d78acbaaf300c1ccbd1c/hadoop-ozone/recon/src/main/java/org/apache/hadoop/ozone/recon/api/handlers/VolumeEntityHandler.java#L168]{*}){*}

Its the same quota in bytes calculation which is being set in API field "Quota 
Allowed" which UI is displaying, so pls check UI code why UI is displaying the 
same backend field under 2 different labels : "{*}Quota In Bytes{*}" and 
"{*}Quota Allowed{*}"

> Recon UI - Disk Usage : Quota Allowed and Quota In Bytes are same and 
> duplicate
> -------------------------------------------------------------------------------
>
>                 Key: HDDS-11987
>                 URL: https://issues.apache.org/jira/browse/HDDS-11987
>             Project: Apache Ozone
>          Issue Type: Bug
>            Reporter: Devesh Kumar Singh
>            Assignee: Abhishek Pal
>            Priority: Major
>         Attachments: image-2024-12-24-10-07-33-326.png, 
> image-2024-12-24-10-07-49-513.png
>
>
> Disk Usage : Quota Allowed and Quota In Bytes both are same and duplicate, 
> Need to show Quota Allowed:
> !image-2024-12-24-10-07-33-326.png|width=281,height=386!
> !image-2024-12-24-10-07-49-513.png|width=356,height=497!
>  
> cc: [~kkasawa] 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to