Hi, Willem
Thanks for your advice, I order my thoughts based on your advice
Time related options:
1.SagaStart.timeout
2.Compensable.timeout
3.Compensable.retires
4.Compensable.retryDelayInMilliseconds
5.Calls.timeout (Include connection timeout and request timeout between
business systems, etc.)
Good job!
sen sun 于2020年1月6日周一 下午11:58写道：
>
> Hi All,
>
> Apache ServiceComb Team is glad to announce the release of Apache
> ServiceComb Toolkit 0.2.0
>
> Apache ServiceComb Toolkit(https://github.com/apache/servicecomb-toolkit)
> is a contract-based microservice development toolkit. It
I think we should not only count the retryDelay time, but also the
compensable time out situation.
If we got the network connection issue, the compensable timeout could
be triggered and we need to deal with it.
How about set the assumption like this
SagaTimeout > (retryDelayInMilliseconds +
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 matter how many retries, the timeout is fixed. So I recommend that the
three attributes of
Hi All,
Apache ServiceComb Team is glad to announce the release of Apache
ServiceComb Toolkit 0.2.0
Apache ServiceComb Toolkit(https://github.com/apache/servicecomb-toolkit)
is a contract-based microservice development toolkit. It provides the
ability to convert and verify contracts, code, and
