qianye1001 opened a new issue, #11153: URL: https://github.com/apache/rocketmq/issues/11153
### Description `NettyRemotingClient` allocates a dedicated `scanExecutor` for NameServer availability probes: 4 core threads, up to 10 threads, and a queue of 32 tasks. The existing housekeeping timer submits a task per address to that pool. Each task calls `getAndCreateChannel()`, which waits for the Netty connection future to complete. These probes only establish or reuse connections. Netty already provides asynchronous connection completion, so the extra worker pool and task queue are unnecessary. ### Expected behavior Initiate probes directly from the existing housekeeping timer and update the available NameServer list in connection-completion callbacks. Remove the scan executor entirely, without replacing it with another executor or timer thread. The timer must not wait for connections or a contended channel-table lock. Pending or failed connections must not be advertised as available, and late callbacks must not restore removed addresses or overwrite newer connection results. Preserve the existing `scanAvailableNameSrv` switch and probe interval. -- 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]
