Currently, calling getConnString() on a ShardRemote object reaches back into the RSM to determine the connection string. This can result in taking an RSM mutex, and so requires care around which mutexes are held when calling getConnString().

However, the reworking of the RSM-related ShardRegistry functionality on SERVER-46202 (specifically _latestConnStrings) means that this behaviour should no longer be necessary. Instead, Shard objects should now be able to simply remember and use the connection string they were created with (ie. what is currently called originalConnString(), which could then go away).