You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2022/02/16 13:32:00 UTC

[jira] [Updated] (HDDS-6333) Add metrics to record the sequence number lag between Recon and OM

     [ https://issues.apache.org/jira/browse/HDDS-6333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ASF GitHub Bot updated HDDS-6333:
---------------------------------
    Labels: pull-request-available  (was: )

> Add metrics to record the sequence number lag between Recon and OM
> ------------------------------------------------------------------
>
>                 Key: HDDS-6333
>                 URL: https://issues.apache.org/jira/browse/HDDS-6333
>             Project: Apache Ozone
>          Issue Type: Improvement
>            Reporter: Janus Chow
>            Assignee: Janus Chow
>            Priority: Major
>              Labels: pull-request-available
>
> In HDDS-6312, Recon is regulated to retrieve a limited number of delta updates from OM, which eliminates the possibility of large delta updates causing OM's OOM.
> We did this control by setting the configuration of "recon.om.delta.update.limit" and "recon.om.delta.update.loop.limit", the default consume speed would be 2000*10 per 10 minutes, but we are not sure if we are consuming at an optimal speed.
> This ticket is to add a metric to record the lag between Recon and OM, which can help to set an appropriate value and prepare for other near real-time works on the Recon side.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org