[GitHub] [hadoop-ozone] hanishakoneru edited a comment on issue #369: HDDS-2755. Compare transactionID and updateID of Volume operations to avoid replaying transactions

[GitBox <gi...@apache.org>]

hanishakoneru edited a comment on issue #369: HDDS-2755. Compare transactionID and updateID of Volume operations to avoid replaying transactions
URL: https://github.com/apache/hadoop-ozone/pull/369#issuecomment-566742756
 
 
   > > > Replay Tx 40 - Vol1 already exists => Tx will throw VOLUME_ALREADY_EXISTS when trying to createVolume
   > > 
   > > 
   > > This also will be considered as replay right?
   > 
   > No. This is not replay. This is another request after the restart. In non-HA after every restart ratisTransactionIndex starts from zero, we have not persisted the value.
   
   Sorry I didnt understand. In non-HA case, we have to handle differently by setting the transactionIndex to LastAppliedIndex. 
   In the example I gave, this is a replay of transaction 40. I have not considered the requests which are received after the restart.
   
   `I have not considered the requests which are received after the restart.`
   Replay means after restart only right. Sorry not understand what you are referring here.

----------------------------------------------------------------
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