You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@servicecomb.apache.org by "cherrylzhao (JIRA)" <ji...@apache.org> on 2018/09/06 07:00:00 UTC

[jira] [Created] (SCB-896) split saga transaction event into hot and cold

cherrylzhao created SCB-896:
-------------------------------

             Summary: split saga transaction event into hot and cold
                 Key: SCB-896
                 URL: https://issues.apache.org/jira/browse/SCB-896
             Project: Apache ServiceComb
          Issue Type: Improvement
          Components: Saga
    Affects Versions: saga-0.3.0
            Reporter: cherrylzhao
             Fix For: saga-0.3.0


split saga transaction event into hot and cold.   
- transaction event table. (Hot)
     storage txEvent receiving from omega directly.
- transaction finished table.(cold)
     When receiving global transaction end instruction.
         - if there does’t exist compensation, 
            move related transaction record to finish table asynchronous.
        - if need compensation, when receiving compensation finished command from omega, 
           move the related event to finished table asynchronous.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)