Details
Description
We set the ClientIsMasterMetadataState with appName here. Unfortunately, that happens after we evaluate failCommand here, so the first isMaster cannot have appName filters be applied to it.
The full solution is most likely to separate parse() from run() for isMaster. However, that is potentially disruptive to backport. The less intrusive answer is to separate the functionality that sets the metadata into its own function. We can then invoke that function in failCommand if we don't have client metadata.
Attachments
Issue Links
- causes
-
SERVER-56935 "ClientMetadata was previously set" invariant in embedded SDK
-
- Closed
-
- is depended on by
-
-
- Closed
-
- is duplicated by
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
SERVER-50804 Make external (application) client info available for commands on shards and config servers
-
- Closed
-
- is related to
-
-
- Closed
-
- related to
-
SERVER-50517 Rename ClientMetadataIsMasterState to ClientMetadataHelloState
-
- Closed
-
-
-
- Closed
-