[
https://issues.apache.org/jira/browse/HDDS-11874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17903653#comment-17903653
]
Devesh Kumar Singh commented on HDDS-11874:
-------------------------------------------
This improvement and both sub-tasks are important for Recon user to be aware
about the state of OM data shown in recon.
> Ozone Recon - Event notifications and metrics for indicating staleness of
> Recon OM Data
> ---------------------------------------------------------------------------------------
>
> Key: HDDS-11874
> URL: https://issues.apache.org/jira/browse/HDDS-11874
> Project: Apache Ozone
> Issue Type: Improvement
> Components: Ozone Recon
> Reporter: Devesh Kumar Singh
> Priority: Major
>
> # Identify staleness of OM data in Recon dashboard and have display
> notification for the respective data stats.
> ** If any Recon OM task current run status shows running and last updated
> sequence number is less than or not equal to last updated sequence number of
> OM delta task, it is evident for Recon to display notification in the UI area
> about stale data which is processed by that respective Recon OM task.
> # Detect the multiple consecutive events of full snapshot sync of Recon OM
> happening from last X number of consecutive Recon OM DB sync task and notify
> at UI about Recon lagging from OM DB and show some warning sign which alerts
> user about staleness and need to watchout logs.
> ** This anomaly detection should also be notified about the overall health
> of Recon OM sync task and OM data lagging in Recon, because ideally there
> should not be consecutive full snapshot events of Recon OM sync and only
> incremental sync should happen.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
