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

Consider replacing CommandOnShardedViewNotSupportedOnMongod mechanism with rewrite / routing from shard

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • Query Optimization

    Description

      When a read against a non-materialized view is performed in a sharded cluster, the read is first sent to the primary shard for the database, which then looks up the view definition and returns to mongos as part of a CommandOnShardedViewNotSupportedOnMongod error response. We could consider instead performing the rewrite locally on the primary shard and then performing shard to shard routing. This would save us a network hop from the primary shard back to mongos.

      Attachments

        Activity

          People

            backlog-query-optimization Backlog - Query Optimization
            james.wahlin@mongodb.com James Wahlin
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

            Dates

              Created:
              Updated: