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 2019/05/05 02:44:00 UTC

[jira] [Created] (SCB-1276) Make saga-actuator execute SQL one by one while integrating with ShardingSphere

cherrylzhao created SCB-1276:
--------------------------------

             Summary: Make saga-actuator execute SQL one by one while integrating with ShardingSphere
                 Key: SCB-1276
                 URL: https://issues.apache.org/jira/browse/SCB-1276
             Project: Apache ServiceComb
          Issue Type: Improvement
          Components: Saga
            Reporter: cherrylzhao
             Fix For: saga-0.4.0


currently, we have integrated with saga using graph based engine in shardingsphere
it need us to collect all participated actual SQL, then submit to saga actuator in commit/rollback phase.
if application crashed before invoking saga actuator, undo log of branch transaction SQL will not be saved, 
so recovery thread will not be executed correctly.

it's better that encapsulating every actual SQL as a saga task in shardingsphere side, 
then submit to saga actuator realtime instead of batch processing all the SQLs at commit/rollback phase. 
this architecture will make the boundary more clear between shardingsphre and saga, currently we have done some additional works for integrating saga.



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