[jira] [Updated] (HDDS-8633) Separate Recon OM Synchronization and Tasks Processing Using Event Queue

["Devesh Kumar Singh (Jira)" <ji...@apache.org>]

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

Devesh Kumar Singh updated HDDS-8633:
-------------------------------------
    Summary: Separate Recon OM Synchronization and Tasks Processing Using Event Queue  (was: Separate Recon OM Synchronization and Tasks Processing)

> Separate Recon OM Synchronization and Tasks Processing Using Event Queue
> ------------------------------------------------------------------------
>
>                 Key: HDDS-8633
>                 URL: https://issues.apache.org/jira/browse/HDDS-8633
>             Project: Apache Ozone
>          Issue Type: Improvement
>          Components: Ozone Recon
>    Affects Versions: 1.3.0
>            Reporter: Ivan Andika
>            Assignee: Devesh Kumar Singh
>            Priority: Major
>              Labels: pull-request-available
>
> It is found when Recon is (re)processing all the Recon Tasks (which may take quite some time), Recon OM DB updates are blocked. After the Recon finished (re)processing tasks, the Recon's last sequence number may have been flushed by the OM, causing full snapshot to be triggered again (this can happen repeatedly).  
> We need to ensure that Recon OM DB is still updated even when Recon Tasks are still in (re)processing phase.



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

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