dubbo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From HouZhiHouJue (GitHub) <git...@apache.org>
Subject [GitHub] [incubator-dubbo] HouZhiHouJue opened issue #3060: Handling timeouts and network timeouts separately
Date Wed, 26 Dec 2018 03:06:33 GMT
There is a difference between timeout and network timeout. In FailoverClusterInvoker, whether
it is timeout or network timeout, it is ignored. If it is a business timeout, then two retry
attempts will cause an avalanche effect. In FailfastClusterInvoker, there is no fault tolerance
for network timeouts. If it is a network partition, the SLA will inevitably fall. I think
the implementation of these two Invokers must include the processing of the network timeout,
otherwise the implementation is not correct.


- [ ] I have searched the [issues](https://github.com/apache/incubator-dubbo/issues) of this
repository and believe that this is not a duplicate.
- [ ] I have checked the [FAQ](https://github.com/apache/incubator-dubbo/blob/master/FAQ.md)
of this repository and believe that this is not a duplicate.

### Environment

* Dubbo version: 2.6.5
* Operating System version: centos 7.2
* Java version: 1.8

### Steps to reproduce this issue

1. xxx
2. xxx
3. xxx

Pls. provide [GitHub address] to reproduce this issue.

### Expected Result

What do you expected from the above steps´╝č

### Actual Result

What actually happens?

If there is an exception, please attach the exception trace:

```
Just put your stack trace here!
```


[ Full content available at: https://github.com/apache/incubator-dubbo/issues/3060 ]
This message was relayed via gitbox.apache.org for notifications@dubbo.apache.org
Mime
View raw message