Investigate whether CollectionShardingRuntime::getOwnershipFilter should stop using getArgsAtClusterTime

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Works as Designed
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      getOwnershipFilter currently gets a metadata set with the timestamp from atCluster parameter. From my understanding, I don't think this is necessarily the timestamp used to read (marjority reads, secondary reads at oplog boundaries). Should this be using RecoveryUnit::getPointInTimeReadTimestamp instead?

            Assignee:
            Unassigned
            Reporter:
            Randolph Tan
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: