zhangwenjian d6309c75be docs📝: state what the draining answer is worth ...

Three comments said readiness failing before the server stops accepting gives
a load balancer the chance to withdraw the instance before its connections are
cut. Nothing between the two lines makes that possible: BeginDraining is
immediately followed by the shutdown, and a poller on a multi-second interval
never observes the flip.

On Kubernetes the endpoint is withdrawn when the Pod receives a
deletionTimestamp, concurrently with SIGTERM and independent of what the probe
returns, so the probe result is not the mechanism there either.

The order itself stands - reporting the state after the connections are cut is
worse - so the comments now say the order is necessary and not sufficient, and
that a window needs a configured delay that does not exist yet.

2026-09-06 19:04:42 +08:00

..

demo.go

feat✨: 新增 app/demo 标准 CRUD 参照模块

2026-08-14 16:46:09 +08:00

jobs.go

format🥚 代码格式化

2021-05-31 18:10:23 +08:00

other.go

format🥚 代码格式化

2021-05-31 18:10:23 +08:00

phase_test.go

fix🐛: check the certificate before announcing that the port is reachable

2026-09-05 22:41:53 +08:00

queue_test.go

fix🐛: register the queue consumers before the queue is started

2026-09-05 22:31:12 +08:00

server_test.go

docs📝: describe the rules rather than who follows them

2026-09-01 19:56:27 +08:00

server.go

docs📝: state what the draining answer is worth

2026-09-06 19:04:42 +08:00

signal_test.go

feat✨: run the BeforeExit callbacks on the way out

2026-09-05 22:31:12 +08:00