Hi, @diecui1202 I checked the code. On 2.6.x, method.async is also passed to the Consumer side. If you just ignore the method.async from the Provider side on the Consumer side (as my pr does), update and start the Provider first, then the method.async will still pass through to the Consumer and affect the Consumer's behavior.
Therefore, for compatibility reasons, it is necessary to fix the problem on the Provider side so that method.async is not registered to the registry. In the Consumer, ignoring the Provider's method.async is equivalent to an insurance, ensuring that the Provider's method.async will not affect the Consumer's behavior under any circumstances. [ Full content available at: https://github.com/apache/incubator-dubbo/issues/2321 ] This message was relayed via gitbox.apache.org for [email protected]
