You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Bharat Viswanadham (Jira)" <ji...@apache.org> on 2020/06/10 20:20:00 UTC
[jira] [Updated] (HDDS-3685) Remove replay logic from actual
request logic
[ https://issues.apache.org/jira/browse/HDDS-3685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bharat Viswanadham updated HDDS-3685:
-------------------------------------
Priority: Critical (was: Major)
> Remove replay logic from actual request logic
> ---------------------------------------------
>
> Key: HDDS-3685
> URL: https://issues.apache.org/jira/browse/HDDS-3685
> Project: Hadoop Distributed Data Store
> Issue Type: Sub-task
> Reporter: Bharat Viswanadham
> Assignee: Bharat Viswanadham
> Priority: Critical
>
> HDDS-3476 used the transaction info persisted in OM DB during double buffer flush when OM is restarted. This transaction info log index and the term are used as a snapshot index. So, we can remove the replay logic from actual request logic. (As now we shall never have the transaction which is applied to OM DB will never be again replayed to DB)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: ozone-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: ozone-issues-help@hadoop.apache.org