PavelZeger opened a new issue, #25898: URL: https://github.com/apache/pulsar/issues/25898
### Search before reporting - [x] I searched in the [issues](https://github.com/apache/pulsar/issues) and found nothing similar. ### Read release policy - [x] I understand that [unsupported versions](https://pulsar.apache.org/contribute/release-policy/#supported-versions) don't get bug fixes. I will attempt to reproduce the issue on a supported version of Pulsar client and Pulsar broker. ### User environment Client Java ### Issue Description `pulsar-client/src/main/java/org/apache/pulsar/client/impl/ControlledClusterFailover.java`: ```java @Override public void close() { this.executor.shutdown(); if (httpClient != null) { try { httpClient.close(); } catch (IOException e) { log.error("Failed to close http client."); } } } ``` The `IOException e` is captured but never logged. When the HTTP client fails to close (which happens on socket leaks, half-closed connections, or shutdown races), the operator sees one line: ``` ERROR ...ControlledClusterFailover - Failed to close http client. ``` and no information about what went wrong. The `IOException` could be: - `SocketTimeoutException` - the connection didn't drain in time. - `IOException("Connection reset")` - the proxy dropped us. - `IOException("Idle eviction failed")` - an internal Jetty error. All three suggest different remedies, and the operator can't tell which without enabling DEBUG logs. When a client transitions away from a cluster, this `close()` runs. Diagnostic information here is the only signal an operator has that the failover happened cleanly. ### Error messages ```text ``` ### Reproducing the issue N/A ### Additional information _No response_ ### Are you willing to submit a PR? - [x] I'm willing to submit a PR! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
