robustness: implement cluster client endpoint switching#21471
robustness: implement cluster client endpoint switching#21471henrybear327 wants to merge 1 commit intoetcd-io:mainfrom
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: henrybear327 The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
Codecov Report✅ All modified and coverable lines are covered by tests. Please upload reports for the commit 5153092 to get more accurate results. Additional details and impacted filessee 47 files with indirect coverage changes @@ Coverage Diff @@
## main #21471 +/- ##
==========================================
- Coverage 68.48% 68.43% -0.05%
==========================================
Files 432 428 -4
Lines 35414 35291 -123
==========================================
- Hits 24253 24152 -101
+ Misses 9758 9738 -20
+ Partials 1403 1401 -2 Continue to review full report in Codecov by Sentry.
🚀 New features to boost your workflow:
|
|
/retest |
9894653 to
4154465
Compare
4154465 to
4f6863f
Compare
995b1f2 to
18929bb
Compare
5793558 to
62787b8
Compare
|
/retest |
|
Can you describe the solution, how it works, what purpose it serve, what are alternatives? |
62787b8 to
2ff45b0
Compare
2a15447 to
3976865
Compare
Signed-off-by: Chun-Hung Tseng <henrytseng@google.com>
3976865 to
5153092
Compare
Introduce optional cluster client endpoint switching.
This would allow us to test out the client reconnection behaviors, such as the resumable guarantee for watches.
Used in #21472