SubConn transitions directly from CONNECTING to IDLE #7862
Labels
Area: Client
Includes Channel/Subchannel/Streams, Connectivity States, RPC Retries, Dial/Call Options and more.
P2
Type: Bug
There is a race when a Subchannel goes from CONNECTING to READY to IDLE that prevents the READY state change notification. We should fix this, as this is causing specific case handling in balancers such as the new pick first leaf policy for DualStack.
The text was updated successfully, but these errors were encountered: