Details
-
Task
-
Resolution: Won't Fix
-
Major - P3
-
None
-
None
-
Sharding 2018-06-18, Sharding 2018-07-02, Sharding 2018-07-16
Description
It currently fails with PooledConnectionsDropped when setFCV is run concurrently with movePrimary.
It seems like it's due to a race condition in between creating a connection between the donor and recipient shards and tagging the connection as kKeepOpen in the NetworkInterfaceTL (so that setFCV does not close the connection with the non-retryable error code PooledConnectionsDropped).
This ticket is to finish investigating the root cause and either unblacklist the workload or update the comment in the places where it is blacklisted.
Attachments
Issue Links
- related to
-
SERVER-44241 Complete TODO listed in SERVER-35534
-
- Closed
-