[PACK] Migrate travis-ci to github workflow completed

* Master pr passed * Master push passed * Deploy snapshot passed (Run at 2 during night UTC) Github issues https://github.com/apache/servicecomb-pack/issues/693 JIRA issues https://issues.apache.org/jira/browse/SCB-2199 https://issues.apache.org/jira/browse/SCB-2205

Re: Apply to Contribute to ServiceComb Pack

Welcome!! Best regards, Lei Zhang On June 18, 2020 at 2:05:23 PM, song Sylvia (sylvia_song2...@outlook.com) wrote: Hi everyone, I’m Xinwei Song, a student studying in a joint program of Beihang University and Beijing University of Technology, majoring in software engineering. I saw the

Re: [VOTE] Release Apache ServiceComb Pack version 0.6.0

+1 binding I checked running the demo against it. Best regards, Lei Zhang On May 22, 2020 at 12:40:21 AM, Mohammad Asif Siddiqui ( asifdxtr...@apache.org) wrote: Hi All, This is a call for Vote to release Apache ServiceComb Pack version 0.6.0 Release Candidate :

Re: [Announce] New committer of ServiceComb

Congratulations!! Best regards, Lei Zhang On May 9, 2020 at 6:39:42 PM, Willem Jiang (willem.ji...@gmail.com) wrote: Hi, I want to introduce humingcheng (Github ID: humingcheng[1]) as a new committer of ServiceComb. He is one of the main author of servicecomb-mesher and has been around the

Re: [PACK][DISCUSS] Resume suspended global transaction

something wrong with the processing, I think > it's better to suspend the transaction processing. > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > On Sat, Apr 18, 2020 at 12:18 AM Zhang Lei wrote: > > > > Hi Team, > > > > Current, the followin

[PACK][DISCUSS] Resume suspended global transaction

Hi Team, Current, the following case will cause global transactions to suspend case 1. Global transaction timeout case 2. Compensate failed case 3. Unpredictable sequence of events Solution case 1: When subsequent events are received, it can resume to the state before suspension and continue

Re: [DISCUSSION][PACK] About forward compensation for FSM

lem On Tue, Jan 7, 2020 at 12:14 AM Zhang Lei wrote: > > Hi, Willem > > Currently, if the timeout property of @Compensable is configured, the Omega > call thread will be interrupted and send TxAbortEvent to Alpha when Omega > call time greater than the timeout. > > No mat

Re: [DISCUSSION][PACK] About forward compensation for FSM

: 姜宁willem On Thu, Jan 2, 2020 at 1:42 AM Zhang Lei wrote: > > Hi, Pack Team > > I recently looked at some forward compensation processing logic and have > some questions > > 1. forward compensation will retry after the call fails until the maximum > number of re

[DISCUSSION][PACK] About forward compensation for FSM

Hi, Pack Team I recently looked at some forward compensation processing logic and have some questions 1. forward compensation will retry after the call fails until the maximum number of retries is exceeded. It calls the reverse compensate applyTo method with each retry. This will cause multiple

[DISCUSSION][PACK] Run Alpha without spring.profiles.active=prd

Hi, Team Currently, this parameter is only used to switch databases between PostgreSQL and MySQL, I suggest using spring.datasource.platform = (mysql/ postgresql) instead, so it looks more clear. I created a JIRA [1] for it. Any suggestions? [1] https://issues.apache.org/jira/browse/SCB-1689

Re: [DISCUSS][PACK] Compensation with combination of forward and reverse

the retries to 0. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Thu, Dec 12, 2019 at 3:03 PM Zhang Lei wrote: > > Hi, Feng Zheng > > Thank you for your reply. > > The question stems from the GitHub issue[1] > > I haven't paid attention to the forward recovery before. When

Re: [DISCUSS][PACK] Compensation with combination of forward and reverse

) wrote: Maybe we can consider to disable the forward recovering with boolean flag instead of setting the retries to 0. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Thu, Dec 12, 2019 at 3:03 PM Zhang Lei wrote: > > Hi, Feng Zheng > > Thank you for your reply. > > The q

Re: [DISCUSS][PACK] Compensation with combination of forward and reverse

Hi, Feng Zheng Thank you for your reply. The question stems from the GitHub issue[1] I haven't paid attention to the forward recovery before. When I optimized the state machine compensation [2] recently, I found that I used retry and timeout incorrectly in the compensation strategy. For this, I

[DISCUSS][PACK] Compensation with combination of forward and reverse

Hi, Pack Team I noticed that forward and reverse cannot be used in combination. If retries == 0 then reverse otherwise forward. I never paid attention to it before until I started thinking about how to define retry and timeout rules for reverse recovery. The purpose of all of this? maybe there

[DISCUSS][PACK] Reverse compensation timeout and retry

Hi, Pack Team I submitted a PR [1] solve send the compensation result to Alpha after Omega slide the compensation method execution is completed. Because Alpha needs to wait for the compensation result after calling the compensation method, in order to avoid waiting indefinitely [2], I have to

Re: Improve the transaction compensation mechanism for FSM

#L35 Best regards, Lei Zhang On November 25, 2019 at 7:49:47 PM, Zheng Feng (zh.f...@gmail.com) wrote: Hi, I wonder how we can diff the "Omega compensation failure" from the "Business compensation failure" ? the different exception classes ? Zhang Lei 于2019年11月25日

Improve the transaction compensation mechanism for FSM

Hi, Pack Team Currently, Alpha compensation mechanism has some defects [1], I plan to solve this problem step by step [2] Step1: Modify the OnConnected method to bidirectional streaming RPC This will be needed for the Step2 Step2: Custom compensation exception rules to distinguish

Improve the transaction compensation mechanism for FSM

Hi, Pack Team Currently, Alpha compensation mechanism has some defects [1], I plan to solve this problem step by step [2] Step1: Modify the OnConnected method to bidirectional streaming RPC This will be needed for the Step2 Step2: Custom compensation exception rules to distinguish

Re: [ANN] ServiceComb Toolkit integrates with SonarCloud.io

Hi, Daniel Qian Good jobs! Best regards, Lei Zhang On November 15, 2019 at 3:36:14 PM, Daniel Qian (chanjars...@gmail.com) wrote: Hi Toolkit team and all, I've finished the ServiceComb Toolkit project's SonarCloud.io integration work[1]. The SonarCloud project page could be found here[2].

Re: Simplify user usage if the OmegaContext parameter is defined in the @SagaStart or @Compensable annotation method

at 12:39 PM Zhang Lei wrote: > > If the user defines the parameter OmegaContext in the method we pass, > otherwise ignore... > > > Best regards, > Lei Zhang > > On November 14, 2019 at 11:56:49 AM, Zheng Feng (zh.f...@gmail.com) wrote: > > In the other word, if the

Re: [Pack] Use Netty native transport improve performance

: > > Thanks a lot for sharing these information and it looks like a great improvement. > > @Willem Jiang can we release the native libraries in the zip files ? > > Zhang Lei 于2019年11月15日周五 下午12:50写道： >> >> Optimize Alpha Performance Using Netty native transport a

[Pack] Use Netty native transport improve performance

Hi, Pack Team Netty provides native socket transport[1] for Linux and macOS, In order to support it, I need to upgrade Netty to the new version. But there are some problems[2] with the SSL test case after the upgrade. Boringssl does not support cipher ECDHE-ECDSA-AES128-SHA256, You can see it in

Re: Simplify user usage if the OmegaContext parameter is defined in the @SagaStart or @Compensable annotation method

nk we can support to let the user pass OmegaContext as null > object when calling the method. > And we can inject the runtime OmegaContext instance to as a parameter > when the parameter is null. > > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > >

Re: Simplify user usage if the OmegaContext parameter is defined in the @SagaStart or @Compensable annotation method

> > > and we also can inject the OmegaContext during invoking the method. > > > > Zhang Lei 于2019年11月13日周三 下午11:42写道： > > > > > Hi, Zheng Feng > > > > > > Both are ok. > > > > > > I saw in [1] that the TransactionContext is passed

Re: Simplify user usage if the OmegaContext parameter is defined in the @SagaStart or @Compensable annotation method

if the invoker doesn't know anything about the OmegaContext. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Tue, Nov 12, 2019 at 11:34 PM Zhang Lei wrote: > > Hi, Pack Team > > Currently, the @Autowired annotation is required to get the OmegaContext on > the Omega

Simplify user usage if the OmegaContext parameter is defined in the @SagaStart or @Compensable annotation method

Hi, Pack Team Currently, the @Autowired annotation is required to get the OmegaContext on the Omega side, but most of the early use does not know the existence of the OmegaContext object. @Autowired OmegaContext omegaContext; @SagaStart public void booking() { omegaContext.globalTxId() ...

Problem with implementing interface SagaMessageSender in the ServiceComb Pack

Hi, Team In the ServiceComb Pack, Classes RetryableMessageSender.java SagaLoadBalanceSender.java and GrpcSagaClientMessageSender.java implement the interface SagaMessageSender. I have two questions: 1. RetryableMessageSender.java unused 2. Both SagaLoadBalanceSender.java and

About simplifying Omega configuration

Hi, Team Currently, Alpha and Omega have some duplicate configurations, such as alpha.feature.akka.enabled=true, I think Omega can get this information through Alpha to simplify configuration. I noticed that the OnConnected method returns a stream object, I have two options: 1. Redefine the

Re: Removing the kamon code from ServiceComb-Pack Alpha Server

I found the configuration of Kamon in the application.conf file, I think that this file is no longer needed. Best regards, Lei Zhang 在 2019年8月16日 上午11:37:31, Willem Jiang (willem.ji...@gmail.com) 写到:

Re: [VOTE] Accept oas-validator to ServiceComb

+1 Best regards, Lei Zhang 在 2019年10月15日 上午11:08:16, Willem Jiang (willem.ji...@gmail.com) 写到: Hi Team, This is a call for vote Accept oas-validator into Apache Software Foundation (ASF) as a part of ServiceComb Toolkit. There is the discussion thread[1] about the donation. Voting will start

Re: Travis CI updated JDK to 11

You can configure the JDK version in .travis.yml file looks like below: ``` language: java jdk: - openjdk8 ``` Lei Zhang > 在 2019年10月8日，下午7:58，bismy 写道： > > Hi, > > > Travis CI updated JDK from 8 to 11, and java-chassis got some compile errors. > Check > > > >

[advice] About the use of JIRA

I found some syntax errors, Is the following category, I can fix this code, but I'm not sure how to create JIRA for this type of problem can look clearer 1. No judgment null pointer 2. Call to equals() comparing different types 3. Exception created and dropped rather than thrown 4. Comparison of

Re: Occasional UnitTest failure in PackIT.compensatesFailedGlobalTransaction

Waiting for more long-term is a problem, you know that CI is sometime very slow, the test case is just to get globalTxId of this transaction and TxEvents List distinctGlobalTxIds = eventRepo.findDistinctGlobalTxId(); assertThat(distinctGlobalTxIds.size(), is(1)); String globalTxId =

Occasional UnitTest failure in PackIT.compensatesFailedGlobalTransaction

The tearDown method is used to clean up the data after each test case is executed. But the compensation method is executed asynchronously, so it is possible to execute after the tearDown method. UnitTest failed log : Running org.apache.servicecomb.pack.integration.tests.PackIT 02:08:47.217

Re: [PROPOSAL] Update the website homepage to make it easier for users to use ServiceComb

+1 I expect it so much Lei Zhang > 在 2019年9月7日，上午12:30，victor chan 写道： > > Hello,all > Recently, I have made a return visit to some users in the community, many > of whom reported that the documents on our website were unfriendly and > imperfect. They are looking forward to our improvement. I

Alpha High-Availability, Distributed Actors prototype verified

Hi Team, I have completed prototype verification fo Akka Cluster [1], I will begin the job this week. The task is as follows: 1. Refactoring model alpha-fsm-channel-kafka and alpha-fsm-channel-redis to alpha-fsm. 2. Use Akka Cluster sharding manage distribute actors. 3. Use Cluster Aware

Re: [DISCUSS] the performance and reliability trade-offs of KafkaMessage Publisher

hich > cannot be send to kafka for further investigation. > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > On Sat, Aug 17, 2019 at 4:11 PM Zhang Lei wrote: >> >> Add another point: >> >> We still use the asynchronous send method.

Re: [DISCUSS] the performance and reliability trade-offs of KafkaMessage Publisher

eption("data must be BaseEvent type"); } } catch (InterruptedException | ExecutionException | UnsupportedOperationException e) { logger.error("publish Exception = [{}]", e.getMessage(), e); throw new RuntimeException(e); } } > 在 2019年

[DISCUSS] the performance and reliability trade-offs of KafkaMessage Publisher

Hi, Team Our previous discussion on PR[1] about using synchronous or asynchronous methods to send Kafka messages, I think need a trade-off in reliability and performance. Maybe we give the option to the user by allowing the user to customize some parameters, I have the following suggestions

Alpha Web manage UI

Hi, Team I added a simple front-end web manage UI to AlPHA, I wrote a manual[1] and Screencast[2]. I can't wait to tell everyone. Please let me know if you have any suggestions. [1] https://github.com/coolbeevip/servicecomb-pack/blob/SCB-1411/docs/fsm/how_to_use_fsm.md

Re: Removing the kamon code from ServiceComb-Pack Alpha Server

Micrometer[1] already integrated into Spring Boot and support for popular monitoring systems. Maybe we can consider using it later. [1] http://micrometer.io/ > 在 2019年8月8日，上午11:27，Willem Jiang 写道： > > Hi, > > Last year we add the Kamon[1] for the measure the

A sample WEB UI for Alpha with Akka

Hi, Team Alpha with Akka version already supports storing transactional data to ES, We need a WEB GUI to display transaction data. The early GUI module seems to have not been updated for a long time, and he only supports querying from the database. The bad news is that I am not good at

Re: [DISCUSSION] Async support for Saga

gt;>> wrote: >>>> >>>> Export the low level API could introduce some error if the user >>>> doesn't use the API rightly. >>>> My suggestion is we just >>>> BTW, I submit a PR[1] to address this issue in a simple way (But we >&

Re: [VOTE] Drop the support of Spring Boot 1.x for ServiceComb-Pack

+1 > 在 2019年7月29日，下午5:41，Willem Jiang 写道： > > Hi Team, > > As we discussed in the this thread[1]. I propose that we drop the > Spring Boot 1.x support both Alpha and Omega side to save some > development resources. > > This voting ends 72 hours from today. > >

Re: [DISCUSSION] Async support for Saga

Hi, Daniel Qian Are you talking about the asynchronous problem with the @SagaStart and @Compensable methods on the Omega side? I think this is a typical long transaction scene. Alpha based on Actor model has implemented asynchronous processing of Omega and Alpha, The event sent to Alpha needs

Re: [DISCUSSION] Alpha Saga transactional data persistence to ElasticSearch

ng that we list >> the features which we want do in this release cycle at the end of this >> August to make sure we can provide a basic runnable Saga coordinator >> on top of state machine solution. >> >> >> Willem Jiang >> >> Twitter: willemjia

Re: Spring Boot 1.x support of ServiceComb-Pack

I agree that alpha only supports spring boot 2.x. However, it is recommended that Omega support both spring boot 1.x and spring boot 2.x. Maybe we only need to include spring boot 2.x in the release version, so we only need to perform the acceptance test of spring boot 2.x version, but allow

[DISCUSSION] Alpha Saga transactional data persistence to ElasticSearch

Hi, all After reimplementing Saga with a state machine, we no longer need to perform complex table scans, so we can use ElasticSearch to persist transaction data. And use the ElasticSearch RESTful API to provide external query capabilities for terminating transactions. 1. Improve the

Re: About alpha-fsm progress

mjiang > Weibo: 姜宁willem > > On Tue, Jul 9, 2019 at 8:21 AM Zhang Lei wrote: >> >> Hi All >> >> I have completed the acceptance test for the state machine and pushed to >> branch SCB-1321 and CI pass. See more feature progress here[1]. >>

Re: About alpha-fsm progress

ance test 4. Verify Akka cluster reliability [1] https://github.com/apache/servicecomb-pack/tree/SCB-1321/alpha/alpha-fsm <https://github.com/apache/servicecomb-pack/tree/SCB-1321/alpha/alpha-fsm> Lei Zhang > 在 2019年6月28日，下午5:50，Zhang Lei 写道： > > Hi, All > > alpha-fsm has

Re: About alpha-fsm progress

Hi, Feng Zheng Thank you for the reply :) > 在 2019年6月28日，下午7:49，Zheng Feng 写道： > > Thanks Zhang Lei, > > Zhang Lei mailto:zhang_...@boco.com.cn>> > 于2019年6月28日周五 下午5:50写道： > >> Hi, All >> >> alpha-fsm has been pushed to the branch SCB-1321

About alpha-fsm progress

ess it > later). > > If Omega cannot talk the message broker, Omega should abort the > transaction processing with transport exception. > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > On Tue, Jun 25, 2019 at 8:42 AM Zhang Lei wrote: >> >&g

Re: [PROPOSAL] create an alpha-fsm moduleI for servicecomb pack

am not sure, but I think Akka's persistence can solve this problem you care about. Of course, this ability needs to be verified Thanks, Zhang Lei > 在 2019年6月24日，上午10:46，赵俊 写道： > > Hi, Zhang Lei > >> A2 : I think we only need to ensure that the message can be reliably >

Re: [PROPOSAL] create an alpha-fsm moduleI for servicecomb pack

ecovery is as same > as before based on database. > > -- > Zhao Jun > Apache Sharding-Sphere & ServiceComb > >> On Jun 21, 2019, at 6:41 PM, Zhang Lei wrote: >> >> Hi, >> >> I have created the alpha-fsm module on branch SCB-13

Re: [PROPOSAL] create an alpha-fsm moduleI for servicecomb pack

tps://github.com/apache/servicecomb-pack/tree/SCB-1321/alpha/alpha-fsm> > 在 2019年6月20日，下午3:25，Zheng Feng 写道： > > Yeah, I think Willem has create one [1] before and do you mind I assign > this issue to you ? > > [1] https://issues.apache.org/jira/browse/SCB-1258 > > Zha

Re: [PROPOSAL] create an alpha-fsm moduleI for servicecomb pack

Hi，Feng Zheng Oh!! I created another JIRA SCB-1321, I saw that you are already associated with SCB-1258, Thank you for it. Lei Zhang > 在 2019年6月20日，下午3:25，Zheng Feng 写道： > > Yeah, I think Willem has create one [1] before and do you mind I assign > this issue to you ?

Re: [PROPOSAL] create an alpha-fsm moduleI for servicecomb pack

ul to create an experimental > branch to add this module but not in the master branch. > > Zhang Lei 于2019年6月19日周三 下午5:42写道： > >> I have completed some of the design and prototype in my github. >> >> In the design document [1] my original idea was that a transacti

Re: [ANN] New ServiceComb committer:Tian XiaoLiang (田晓亮)

Welcome～ > 在 2019年6月20日，上午9:25，Willem Jiang 写道： > > Please join me and the rest of the ServiceComb PMC members in welcoming our > new ServiceComb committer: Tian Xiaoliang (田晓亮). > > Tian Xiaoliang has been with Apache ServiceComb for more than one > years by reviewing the code of

Re: [PROPOSAL] create an alpha-fsm moduleI for servicecomb pack

I have completed some of the design and prototype in my github. In the design document [1] my original idea was that a transaction consisted of a SagaActor and several TxActors, and later TxAcotr was removed to reduce implementation complexity. I haven't had time to modify the documentation

Re: [PROPOSAL] create an alpha-fsm moduleI for servicecomb pack

How can I change the document? I have not the permissions to edit this document. Lei Zhang > 在 2019年6月19日，上午11:42，Willem Jiang 写道： > > Hi Zhang Lei, > > It's great to hear from you for the proposal. Do you mind share us > more detail about the alpha-fsm module? > If

[PROPOSAL] create an alpha-fsm moduleI for servicecomb pack

We plan to use the state machine to track transaction status in the wiki [1]. I think we can create a state machine prototype and test it by creating a new alpha-fsm module in alpha. I have completed the basic prototype and test cases of the state machine based on AKKA. I want to share with you

Re: Announce of new ServiceComb PMC member

Congratulations. Lei Zhang > 在 2019年6月10日，上午10:53，Willem Jiang 写道： > > It is very rewarding to see that most of the contributors who became > committers continue to stay involved. Therefore, in recognition of > their continued contribution, the Apache ServiceComb PMC invited > recently a

Re: [Saga] A little thought about Using StateMachine for tracing the transaction states

message broker is good choice Lei Zhang > 在 2019年5月15日，上午10:03，Willem Jiang 写道： > > the message broker

Re: [Saga] A little thought about Using StateMachine for tracing the transaction states

add more states. > But ZhangLei showed us a fantastical document for checking the states > of Saga use case. > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > On Tue, May 14, 2019 at 3:49 PM Zheng Feng wrote: >> >> Thanks Zhang Lei - i

Re: [Saga] A little thought about Using StateMachine for tracing the transaction states

vip/playground/blob/master/state_machine_demo/saga-akkafsm/README.md> Lei Zhang > 在 2019年5月14日，下午3:48，Zheng Feng 写道： > > Thanks Zhang Lei - it is really great work ! > > I think we could describe every event and state with more details, e.g. > SagaStartedEvent: it is the

[Saga] A little thought about Using StateMachine for tracing the transaction states

I wrote a preliminary design [1] based on wiki [2], , Maybe not perfect or something I don't know. Any suggestions? [1] https://github.com/coolbeevip/playground/blob/master/state_machine_demo/saga-akkafsm/README.md

[QUESTION] After the Saga transaction compensation method call fails, will it repeat until it succeeds?

Lei Zhang

Re: [Saga] About Omega's timeout process

Hi, Willem Jiang You mean that Thread.interrupt will cause the variables in the thread to be lost, so we need to provide a way for the user to restore the thread variables? Lei Zhang > 在 2019年4月26日，上午8:36，Willem Jiang 写道： > > We could introduce a Context object to let the user copy the

Re: [Saga] About Omega's timeout process

In my example, I defined a runtime exception TimeoutAspectException, user can know that a timeout has occurred when catching the exception The following unit test case tested a custom exception TimeoutAspectException @Test(expected = TimeoutAspectException.class) public void

[Saga] About Omega's timeout process

At present, Omega's timeout only stores to the database, find timeout Tx transactions and compensation through database scans. This may cause the commit of the Tx transaction after the compensation. I think it can be improved TransactionAspect class, Terminates the execution of the method when