From: sergiyvamz (@sergiyvamz) <noreply+sergiyvamz@github.com>
To: aws/aws-advanced-jdbc-wrapper <noreply+aws-aws-advanced-jdbc-wrapper@github.com>
Subject: Re: [aws/aws-advanced-jdbc-wrapper] PR #2237: feat: add efm3 host monitoring plugin with per-connection registration
Date: Wed, 18 Nov 2026 22:52:53 +0000
Message-ID: <gh-aws-aws-advanced-jdbc-wrapper-2237-rc4621968297@github.com> (raw)
In-Reply-To: <gh-aws-aws-advanced-jdbc-wrapper-2237-rc4621290393@github.com>
References: <gh-aws-aws-advanced-jdbc-wrapper-2237@github.com>
<gh-aws-aws-advanced-jdbc-wrapper-2237-rc4621290393@github.com>
(on wrapper/src/main/java/software/amazon/jdbc/plugin/efm/v3/HostMonitorV3Impl.java:407)
The probe count is already in the verdict: the host is only marked unhealthy after failureDetectionCount consecutive failed probes, and probing starts once some call has passed failureDetectionTime. So the first call is aborted at roughly failureDetectionTime + (count - 1) x interval. This check only decides which calls are eligible once the host is known to be down. A call that passes the grace period while the host is still failing is aborted then, which is what efm2 does with contexts that become active while the node is unhealthy. Adding count x interval per call would let calls to a host we already know is down run for another full detection cycle.