api: add /health/unhealthy endpoint to mark the instance as unhealthy#1141
api: add /health/unhealthy endpoint to mark the instance as unhealthy#1141YangKeao wants to merge 1 commit intopingcap:mainfrom
/health/unhealthy endpoint to mark the instance as unhealthy#1141Conversation
|
Skipping CI for Draft Pull Request. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: 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 |
c84bc10 to
dca63c4
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1141 +/- ##
=======================================
Coverage ? 67.44%
=======================================
Files ? 149
Lines ? 16128
Branches ? 0
=======================================
Hits ? 10878
Misses ? 4514
Partials ? 736
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Signed-off-by: Yang Keao <yangkeao@chunibyo.icu>
dca63c4 to
bf6e505
Compare
What problem does this PR solve?
Issue Number: close #1140
Problem Summary:
For the LB from cloud provider, once the Pod enters
terminatingstatus, the connection will persist at most 15min (for aliyun) and 1h (for AWS). However, forunhealthy, the connection can be persisted for a very long time: 100h for AWS and not limited for Aliyun (I've only tested for 1h, and I'll try 24h tests later).What is changed and how it works:
Check List
Tests
Notable changes
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.