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

Routing information must be forcefully refreshed on the router for the WouldChangeOwningShardBatchWrite.yml Genny workload

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.1.0-rc0
    • Affects Version/s: 4.4.0, 5.0.0
    • Component/s: None
    • None
    • Catalog and Routing
    • Fully Compatible
    • ALL
    • Hide

      A similar jstest (on v5.0) is here and I see the same error when I remove the flushRoutersAndRefreshShardMetadata().
      In 6.0 onwards, the router automatically refreshes its routing information after a moveChunk operation (and that's why we see the failures in v4.4 and v5.0 consistently); this can be confirmed by removing the flushRoutersAndRefreshShardMetadata()]. 

      Show
      A similar jstest (on v5.0) is  here and I see the same error when I remove the  flushRoutersAndRefreshShardMetadata() . In 6.0 onwards, the router automatically refreshes its routing information after a moveChunk operation (and that's why we see the failures in v4.4 and v5.0 consistently); this can be confirmed by removing the flushRoutersAndRefreshShardMetadata() ]. 
    • CAR Team 2024-04-29, CAR Team 2024-05-13, CAR Team 2024-05-27, CAR Team 2024-06-10, CAR Team 2024-07-22
    • 0
    • 2

      The error is that shard rs1 throws the following error when rs1 receives the updateOne request after the split & moveChunk operation in phase0

      Update operation was converted into a distributed transaction because the document being updated would move shards and that transaction failed. :: caused by :: Encountered error from 10.2.0.202:27017 during a transaction :: caused by :: this shard no longer contains chunks for test.Collection0, the collection may have been dropped: generic server error

      This is because mongos does not have the updated shard version after the  split & moveChunk operation and it must be forcefully refreshed in the genny workload (as done in jstests using the flushRoutersAndRefreshShardMetadata cmd).

       

            Assignee:
            tommaso.tocci@mongodb.com Tommaso Tocci
            Reporter:
            nandini.bhartiya@mongodb.com Nandini Bhartiya
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: