[
https://issues.apache.org/jira/browse/HDDS-17789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Attila Doroszlai resolved HDDS-17789.
-------------------------------------
Fix Version/s: 2.3.0
Resolution: Fixed
> [Recon] Heatmap API omits color for keys with very low read counts
> ------------------------------------------------------------------
>
> Key: HDDS-17789
> URL: https://issues.apache.org/jira/browse/HDDS-17789
> Project: Apache Ozone
> Issue Type: Bug
> Components: Ozone Recon
> Reporter: Chi-Hsuan Huang
> Assignee: Andy Huang
> Priority: Minor
> Labels: pull-request-available
> Fix For: 2.3.0
>
>
> The Recon heatmap API ({{/api/v1/heatmap/readaccess}}) drops the {{color}}
> field for a leaf whose read ratio truncates to 0, which happens when a key is
> read less than 0.1% as often as the hottest key in its bucket.
> {{EntityReadAccessHeatMapResponse.color}} is annotated with
> {{@JsonInclude(NON_DEFAULT)}}, so 0.0 is never serialized.
> Clients then cannot tell a cold leaf from a missing value, and a chart that
> falls back to a default color can render the coldest key as the hottest.
> HDDS-17693 works around this in the UI by defaulting a missing leaf color to
> 0.
> Proposed fix: always serialize {{color}} on leaves, so a cold key arrives as
> {{"color": 0}}. The UI default added in HDDS-17693 can then be removed.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]