transaction is executed normally. At
>>>> present, the compensation method based on table scan is also asynchronous.
>>>> I am not sure if I have answered your question, or you can give me more
>>>> information.
>>>>
>>>> Q2 : Also we
]
>>>>>
>>> https://github.com/coolbeevip/playground/blob/master/state_machine_demo/saga-akkafsm/assets/saga_state_diagram.png
>>>>> <
>>>>>
>>> https://github.com/coolbeevip/playground/blob/master/state_machine_demo/saga-akkafsm/assets/saga_st
t; Current we won't change the protocol between Omega and Alpha.
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Wed, Jun 19, 2019 at 2:35 PM zhaojun wrote:
>>
>> Hi, Zhang Lei,
>>
>> If we use AKKA, how can we design th
Hi, Zhang Lei,
If we use AKKA, how can we design the actors, and how can we guarantee omega
will receive the message synchronize.
Best Regards
--
Zhao Jun
Apache Sharding-Sphere & ServiceComb
> On Jun 19, 2019, at 11:42 AM, Willem Jiang wrote:
>
> Hi Zhang Lei,
>
> It's grea
I have just created a issue[1] in JIRA
[1]: https://issues.apache.org/jira/browse/SCB-1276
<https://issues.apache.org/jira/browse/SCB-1276>
--
Zhao Jun
Apache Sharding-Sphere & ServiceComb
> On May 5, 2019, at 8:46 AM, zhaojun wrote:
>
> OK, I’ll try to
Willem Jiang wrote:
>>>
>>> We could do some enhancement on it.
>>> From my understanding, We could create a calling graph which has three
>>> sub graph of it, or we could let the SQL executor running the command
>>> one by one.
>>> Any tho
: 姜宁willem
>
> On Mon, Apr 29, 2019 at 7:58 PM zhaojun wrote:
>>
>> Hi, Willem
>>
>> Saga actuator could not compatible with ShardingSphere currently, there are
>> 2 main problem exist.
>> 1. If sql execute in saga transport instead of Shardi
he distributed transaction. But that introduce another
> endpoint(Alpha) to shardingsphere.
>
> From my understanding, Saga actuator is most efficient way to execute
> the SQL across different data nodes.
>
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
&
s://github.com/seata/seata/issues/714
>>
>> Sheng Wu 于2019年4月26日周五 下午6:47写道：
>>
>>> Please be advised, SkyWalking and seata integration are ongoing too.
>>>
>>> https://github.com/seata/seata/issues/714
>>>
>>> SkyWalking agent even
Hi, all
currently, we have integrated with saga using graph based engine in
shardingsphere[1]
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 n
Congratulations~
--
Zhao Jun
Apache Sharding-Sphere & ServiceComb
> On Apr 2, 2019, at 11:11 AM, wjm wjm wrote:
>
> Congratulations~
>
> bismy 于2019年4月2日周二 上午10:46写道：
>
>> Great!
>>
>>
>>
>>
>> -- 原始邮件 --
>> 发件人: "Sure";
>> 发送时间: 2019年4月2日
The paper is excellent, thanks for share!
--
Zhao Jun
Apache Sharding-Sphere & ServiceComb
> On Mar 19, 2019, at 11:40 AM, Willem Jiang wrote:
>
> Yeah, it's an exciting news.
> I just found another paper[1] of Phil after went through the news.
>
> Using Akka to rewrite the Alp
I’ll try to refactor the code in my local repo today.
Please feel free if you have any advice.
--
Zhao Jun
Apache Sharding-Sphere & ServiceComb
> On Jan 15, 2019, at 11:37 AM, zhaojun wrote:
>
> Hi, Willem
>
> Thanks for the comment.
>
> 1.
se, I think we just need to find a way to reuse this code in
> none Spring Boot application.
> 3. +1 to create the Transaction Engine in the Omega Core.
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Mon, Jan 14, 2019 at 7:38 PM zhaojun wrote:
>
I have made omega design for this issue[1], please feel free to give me some
advice.
[1]
https://cwiki.apache.org/confluence/display/SERVICECOMB/refactor+design+of+service-comb+pack+omega
--
Zhao Jun
Apache Sharding-Sphere & ServiceComb
> On Jan 14, 2019, at 5:27 PM,
I have created SCB-1113[1] to track this issue.
[1] https://issues.apache.org/jira/browse/SCB-1113
--
Zhao Jun
Apache Sharding-Sphere & ServiceComb
> On Jan 14, 2019, at 5:21 PM, zhaojun wrote:
>
> OK, let me create a JIRA, and try to refactor it
>
> --
PI, then wrap it with Spring Boot
> Starter API.
> In this way we could support to inject the Omega context not only to
> the Spring Boot Application but also Spring Application.
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Mon, Jan 14, 2019 at 3
Hi, all
I think we should provide api way to bootstrap omega and alpha.
Now our code was tightly coupled with spring-boot, it is not possible for
integrated with other middleware.
We should provide Omega.init(), Alpha.init() api, spring-boot was just one
implementation for Pack.
Any thought?
-
I have got it, it’s necessary to build a pre-write mechanism for these scenario.
> On Jan 8, 2019, at 7:14 PM, Longchun Zhang wrote:
>
> Hi Zhao Jun,
>
> If the omega didn't send any request to Alpha server, the Alpha server
> would not send any compensation command to it later because Alpha
>
Hi, Zhang
Now Alpha side have a timeout mechanism to avoid this happen.
If a global transaction have exceeded timeout setting, alpha will send
compensation command to terminate this transaction.
We also consider about writing event log in omega side to reduce complexity of
alpha side.
---
+1
--
Zhao Jun
Apache Sharding-Sphere & ServiceComb
> On Dec 30, 2018, at 2:12 PM, Jean-Baptiste Onofré wrote:
>
> +1 (binding)
>
> Quickly checked signatures, legal files and headers.
>
> Regards
> JB
>
> On 29/12/2018 12:38, Mohammad Asif Siddiqui wrote:
>> Hi All,
>>
>> T
Hi, Willem
Glad to hear of pack will officially publish first time.
There is not any significant patch need to be merged in my side.
--
Zhao Jun
Apache Sharding-Sphere & ServiceComb
> On Dec 28, 2018, at 3:12 PM, Willem Jiang wrote:
>
> Hi Team，
>
> ServiceComb Saga is renam
Hi, all
I just list some TCC work we should do within service-comb-pack in my side,
And we should make a priority level for these task to make sure we can publish
TCC for lately.
1. try to write event log in omega side to make time-out mechanism lightweight
Actually we haven’t persistence c
+1
> On Dec 15, 2018, at 10:31 PM, Mohammad Asif Siddiqui
> wrote:
>
> Hi All,
>
> This is a call for Vote to release Apache ServiceComb Saga Actuator version
> 0.3.0
>
> Release Candidate :
> https://dist.apache.org/repos/dist/dev/servicecomb/servicecomb-saga-actuator/0.3.0/
>
>
>
Hi, all
Next monday (11/26) is ok for me, I’ll be online at 14:00 (CST) ~ 19:30(CST).
--
Zhao Jun
Apache Sharding-Sphere & ServiceComb
> On Nov 22, 2018, at 3:11 PM, Willem Jiang wrote:
>
> Hi Asif,
>
> Thanks for start up the page.
> I'd like to move the meeting to next Mond
25 matches
Mail list logo
