TeslaCN opened a new issue, #21125: URL: https://github.com/apache/shardingsphere/issues/21125
## Feature Request ### Problems with the current broadcast table In a transaction, the request to query the broadcast table alone will be randomly routed to multiple different data sources, which increases the number of connections occupied by the transaction and the transaction execution delay.  ### Root cause The kernel does not know which data source connections have been cached by the connection manager, so there is no guarantee that the next broadcast table or other unicast statements can reuse the cached connection. Related codes: https://github.com/apache/shardingsphere/blob/dbac9a8cd313120393d122847e42fa6f8fb89dce/shardingsphere-features/shardingsphere-sharding/shardingsphere-sharding-core/src/main/java/org/apache/shardingsphere/sharding/route/engine/type/unicast/ShardingUnicastRoutingEngine.java#L106-L108 ### Idea Provide ShardingUnicastRoutingEngine with preferred data source names. Passed to ShardingUnicastRoutingEngine via ConnectionContext.  -- 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]
