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

Posted to issues@servicecomb.apache.org by "Willem Jiang (JIRA)" <ji...@apache.org> on 2019/04/02 09:07:00 UTC

[jira] [Updated] (SCB-896) Split saga transaction event into hot and cold

     [ https://issues.apache.org/jira/browse/SCB-896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Willem Jiang updated SCB-896:
-----------------------------
    Fix Version/s:     (was: pack-0.4.0)
                   pack-0.3.0

> 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
>            Reporter: cherrylzhao
>            Assignee: cherrylzhao
>            Priority: Major
>             Fix For: pack-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)