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:56 +0000
Message-ID: <gh-aws-aws-advanced-jdbc-wrapper-2237-rc4621968699@github.com> (raw)
In-Reply-To: <gh-aws-aws-advanced-jdbc-wrapper-2237-rc4621444914@github.com>
References: <gh-aws-aws-advanced-jdbc-wrapper-2237@github.com>
<gh-aws-aws-advanced-jdbc-wrapper-2237-rc4621444914@github.com>
(on wrapper/src/main/java/software/amazon/jdbc/plugin/efm/v3/HostMonitoringConnectionPluginV3.java:211)
You're right, a persistent failure made the connection unusable. efm and efm2 avoid that by caching the endpoint before identifying, and efm3 now does the same: the call that hits the error fails, and afterwards the connection is monitored through its endpoint without retrying identification. The javadoc describes this. I kept the efm/efm2 behaviour rather than passing calls through unmonitored so efm3 stays a drop-in replacement. The endpoint-follows-DNS concern applies to all three plugins, so I'd rather handle it separately.