Deregistration Delayとは?
deregistration delayは、connection drainingとも呼ばれ、load balancerがbackendをローテーションから完全に外す前に待機する間隔です。この期間中、新しいリクエストの送信を止めつつ、既存のものは完了させます。これにより、インスタンスが置き換えられたりscale inされたりするときにアクティブな接続を切断することを防ぎます。
なぜ重要か
drainingは、deployやscale-downの間のリクエストの取りこぼしや壊れた応答を回避します。短すぎると遅いリクエストを切断し、長すぎるとrolloutが停滞します。
Where this shows up in a real pipeline
A definition is only useful if you can recognise the thing in your own logs. In practice this concept surfaces when a job behaves differently between a local run and a runner, which is where most CI debugging starts.
- Compare a local run against a CI run of the same command before assuming a tool is at fault.
- Runner environments differ in shell, PATH, TTY availability, available memory, and disk. Most CI-only behaviour traces to one of those five.
- Pin tool versions so an environment difference cannot be introduced by an unrelated update.
よくある質問
What is What is deregistration Delay??
Deregistration delay, also called connection draining, is the interval a load balancer waits before fully removing a backend from rotation. During this window it stops sending new requests but lets existing ones complete. This prevents cutting off active connections when an instance is being replaced or scaled in.
Why does What is deregistration Delay? matter in CI/CD?
Draining avoids dropped requests and broken responses during a deploy or scale-down. Setting it too short cuts off slow requests; too long stalls the rollout.
関連ガイド
What Is commitlint?commitlint is a tool that checks commit messages against a configured convention, rejecting commits that do
What Is Traffic Mirroring?Traffic mirroring sends a copy of live requests to a second service for testing while the original still
What Is a Suspense Boundary?A suspense boundary wraps part of a UI so that while its data or code is loading, a fallback is shown,