You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by GitBox <gi...@apache.org> on 2019/12/05 22:33:54 UTC

[GitHub] [hadoop-ozone] bharatviswa504 opened a new pull request #316: WIP:HDDS-2680. Fix updating lastAppliedIndex in OzoneManagerStateMachine.

bharatviswa504 opened a new pull request #316: WIP:HDDS-2680. Fix updating lastAppliedIndex in OzoneManagerStateMachine.
URL: https://github.com/apache/hadoop-ozone/pull/316
 
 
   ## What changes were proposed in this pull request?
   
   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.
   
   ## What is the link to the Apache JIRA
   
   https://issues.apache.org/jira/browse/HDDS-2680
   
   ## How was this patch tested?
   
   Trying to add some UT's to test this.
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

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