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 2019/12/05 22:33:00 UTC
[jira] [Created] (HDDS-2680) Fix updating lastAppliedIndex in
OzoneManagerStateMachine
Bharat Viswanadham created HDDS-2680:
----------------------------------------
Summary: Fix updating lastAppliedIndex in OzoneManagerStateMachine
Key: HDDS-2680
URL: https://issues.apache.org/jira/browse/HDDS-2680
Project: Hadoop Distributed Data Store
Issue Type: Bug
Reporter: Bharat Viswanadham
Assignee: Bharat Viswanadham
This Jira is to fix a bug that has been caused by HDDS-2637.
Now we have applyTransactionMap where we put all entries of ratisTransactionIndex before complete.
And when updating lastAppliedIndex, now there is a chance that we updateLastAppliedIndex before DoubleBuffer flush has committed transactions to DB.
Let's take 1-10 are apply transaction entries which are not flushed, 11th is indexUpdate a metadata/conf entry transaction, now when notifyIndexUpdate is called with 11, we updateLastAppliedIndex to 11. (Which we should not do) This Jira is to fix this issue.
--
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