finefuture opened a new pull request, #13240: URL: https://github.com/apache/dubbo/pull/13240
## What is the purpose of the change Threshold=number of valid nodes after change/number of original valid nodes. Assuming a threshold of 0.3: 1. The original 100 valid nodes received an event: 80 valid nodes offline, 20/100 less than the threshold of 0.3, discarding this change 2. The original 100 valid nodes have received an event: 50 valid nodes offline, with 50/100 exceeding the threshold of 0.3. Process this change 3. There are 100 original nodes, including 50 valid nodes and 50 unavailable nodes. Received event: 80 offline nodes (40 valid nodes+40 unavailable nodes), with 10/50 less than the threshold of 0.3. Discard this change 4. There are 100 original nodes, including 50 valid nodes and 50 unavailable nodes. Received event: 80 offline nodes (30 valid nodes+50 unavailable nodes), 20/50 is greater than the threshold of 0.3. Process this change 5. There are 100 original nodes, including 50 valid nodes and 50 unavailable nodes. Received event: 50 offline nodes (50 valid nodes), 0/50 is less than the threshold of 0.3, discard this change 6. There are 100 original nodes, including 50 valid nodes and 50 unavailable nodes. Received event: 50 offline nodes (10 valid nodes+40 unavailable nodes), with 40/50 exceeding the threshold of 0.3. Process this change Scenario: 1. Provider publishing or scaling requires mass publishing, and the threshold will be lower than the normal threshold > - It is necessary to have all upstream users change the threshold for this appkey 2. Due to the special nature of the business, the consumer service needs to adjust the threshold, such as the core service wanting to adjust the threshold higher to ensure the success rate of the call > - It is necessary to change the default threshold for all appkeys in this service Priority: provider>consumer>default ## Brief changelog After the registration center recovers from a failure, all temporary nodes will be re registered, and a smaller number of nodes will be pushed to the consumer (such as events for one node or two nodes). If the consumer refreshes the list, it will result in only a few nodes receiving traffic, and in high traffic situations, a large number of reject exceptions will occur, causing traffic loss ## Verifying this change <!-- Follow this checklist to help us incorporate your contribution quickly and easily: --> ## Checklist - [x] Make sure there is a [GitHub_issue](https://github.com/apache/dubbo/issues) field for the change (usually before you start working on it). Trivial changes like typos do not require a GitHub issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue. - [ ] Each commit in the pull request should have a meaningful subject line and body. - [ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why. - [ ] Check if is necessary to patch to Dubbo 3 if you are work on Dubbo 2.7 - [ ] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add sample in [dubbo samples](https://github.com/apache/dubbo-samples) project. - [ ] Add some description to [dubbo-website](https://github.com/apache/dubbo-website) project if you are requesting to add a feature. - [ ] GitHub Actions works fine on your own branch. - [ ] If this contribution is large, please follow the [Software Donation Guide](https://github.com/apache/dubbo/wiki/Software-donation-guide). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
