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

Call supportsReadConcern for all commands in mongos

    • Cluster Scalability

      Currently mongos only checks supportsReadConcern() for a command when it is received with snapshot level read concern, otherwise deferring the check to mongod. As mongos starts to make more decisions based on read concern (e.g. global snapshot timestamp selection) and for consistency of validation, we should consider always performing this check on mongos instead. This would require verifying / adding correct supportsReadConcern() definitions for each cluster command.

            Assignee:
            backlog-server-cluster-scalability [DO NOT USE] Backlog - Cluster Scalability
            Reporter:
            jack.mulrow@mongodb.com Jack Mulrow
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: