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

Stale Shard Version errors are not retried if another error is returned

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Gone away
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • Labels:
      None
    • ALL
    • Hide

      1. Set up a cluster with 3 shards
      2. Shard a collection with the shard0 as the primary shard
      3. Set the shards as read only
      4. Issue a remove or an update wihtout the shard key

      Show
      1. Set up a cluster with 3 shards 2. Shard a collection with the shard0 as the primary shard 3. Set the shards as read only 4. Issue a remove or an update wihtout the shard key
    • Sharding 2020-01-13, Sharding 2020-01-27
    • 20

      On the readonly_sharded test suite, the write_ops test tries all the write operations with ordered:false parameter having the shards set as read only. If the first shard is the primary, then several errors are returned and this is parsed in write_ops.cpp and changed to error MultipleErrorsOccurred (65). It should retry all the SSV errors and only leave the IllegalOperation to be parsed at the executeBatch function. Write a unittest for this.

            Assignee:
            marcos.grillo@mongodb.com Marcos José Grillo Ramirez
            Reporter:
            marcos.grillo@mongodb.com Marcos José Grillo Ramirez
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: