[GitHub] [servicecomb-pack] coolbeevip commented on issue #499: [SCB-1376] Use the internal event to trigger SagaActor stop

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

coolbeevip commented on issue #499: [SCB-1376] Use the internal event to trigger SagaActor stop
URL: https://github.com/apache/servicecomb-pack/pull/499#issuecomment-511262133
 
 
   > It looks when SagaActor is in the Suspended status then it will switch stopped stated.
   > What if we need to keep the status information of Suspended into DB first?
   
   SagaActor will call stopSagaData method of SagaDataExtension after stopped, we can persist here.
   
   > What if there is another event is fired which could bring the Suspended SagaActor into other status.
   
   There are two possibilities for entering the suspended state, the first is a timeout, and the second is an abnormal event sequence.
   **timeout to suspended:** Only when the timeout parameter is set will it enter the suspended state because of the timeout. If the timeout parameter is less than the request timeout, an exception will be thrown to the user.
   **abnormal event sequence:** We don't need to pay attention to subsequent events
   

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