Determine if readPreference should be part of query stats key when making queries against replica sets

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Query Integration
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      When the shell makes a query against a replica set, the query stats key included the `$readPreference` field even if it's not explicitly included in the command (according to slow query logs). This doesn't happen in the standalone or sharded cluster cases. We want to minimize differences in query stats from different kinds of deployment, so ideally this wouldn't happen.

            Assignee:
            Unassigned
            Reporter:
            Ryan Berryhill
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: