[ https://issues.apache.org/jira/browse/HDDS-7960 ]


    smita deleted comment on HDDS-7960:
    -----------------------------

was (Author: JIRAUSER294888):
1. Change the API signature to take path as input instead of all 3 (volume, 
bucket, path). This "path"
will be used as input to Solr query for "resName".
2. Another input on UI for user to provide "Resource Type" which will have only 
3 valid values (Volume, Bucket, Key). This willl be used as input to Solr Query 
as "resType".
3. Either user has to select "path" or "resType" as input. If both provided, 
then "path" will take higher precedence.
4. Take input from UI for "HeatMap Based On Last <24H or 7Days or 90 Days or 
Custom Date Selector which
cannot be more than 90 Days> Access MetaData".

> Recon:  POC for Treemap for Buckets Volumes and Paths
> -----------------------------------------------------
>
>                 Key: HDDS-7960
>                 URL: https://issues.apache.org/jira/browse/HDDS-7960
>             Project: Apache Ozone
>          Issue Type: Task
>          Components: Ozone Recon
>    Affects Versions: 1.2.1
>            Reporter: smita
>            Assignee: smita
>            Priority: Major
>         Attachments: image-2023-02-27-12-42-26-776.png, screenshot-1.png
>
>
> This requirement is to add a capability in Recon to tag storage entities at 
> volume level, bucket level, key level, directory/sub-directory and file level 
> for their access heat. In other words, recon should be able to tag entities 
> with {*}Most Frequently Accessed (MFA), Frequently Accessed (FA) and Less 
> Frequently Accessed (LFA) or Cold data{*}. This will help admin users 
> determine the access pattern of various entities which will in turn help in 
> tiering (Hot, Warm, Cold) of ozone data. Access pattern or heat can be 
> determined based on both READ and WRITE operations on entities.



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