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

Ensure new shard key pattern is used for extracting document key in oplog entries for change streams to consume post refineCollectionShardKey

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Minor - P4 Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: Change streams, Sharding
    • None
    • Catalog and Routing

      The refineCollectionShardKey command does not cause each of the shards to refresh. This means until the shard happens to refresh its sharding metadata from the config server for another reason, it will continue to use the pre-refined shard key pattern. Oplog entries generated by the replica set shard primary won't include the newly-added suffix fields to the shard key pattern until the shard has refreshed. The documentKey field reported in change events in based on the fields extracted and recorded in the oplog entry and therefore can lead to a sequence where change events after the refineCollectionShardKey change event won't include the newly-added suffix fields to the shard key pattern.

            Assignee:
            backlog-server-catalog-and-routing [DO NOT USE] Backlog - Catalog and Routing
            Reporter:
            max.hirschhorn@mongodb.com Max Hirschhorn
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: