Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-49336

Set client metadata if it is missing during failCommand

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.9.0, 4.2.15, 4.4.7
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • v4.4, v4.2
    • Service arch 2020-10-19
    • 133

      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.

            Assignee:
            ben.caimano@mongodb.com Benjamin Caimano (Inactive)
            Reporter:
            ben.caimano@mongodb.com Benjamin Caimano (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: