[
https://issues.apache.org/jira/browse/HDDS-8633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Andika updated HDDS-8633:
------------------------------
Description:
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 processing(reprocessing) phase.
was:
It is found when Recon is reprocessing all the Recon Tasks (which may take
quite some time), Recon OM DB updates are blocked. After the Recon finished
reprocessing 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 processing(reprocessing) phase.
> Separate Recon OM Synchronization and Tasks Processing
> ------------------------------------------------------
>
> 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: Ivan Andika
> Priority: Major
> Fix For: 1.4.0
>
>
> 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 processing(reprocessing) phase.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
