[
https://issues.apache.org/jira/browse/HDDS-8633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Janus Chow updated HDDS-8633:
-----------------------------
Fix Version/s: (was: 1.4.0)
Target Version/s: 1.5.0 (was: 1.4.0)
I am managing the 1.4.0 release and we currently have more than 500 issues
targeted for 1.4.0. I am moving the target field to 1.5.0.
If you are actively working on this jira and believe this should be targeted
for the 1.4.0 release, Please reach out to me via Apache email or Slack.
> 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
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
