Call supportsReadConcern for all commands in mongos

XMLWordPrintableJSON

    • Cluster Scalability
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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:
              [DO NOT USE] Backlog - Cluster Scalability
              Reporter:
              Jack Mulrow
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: