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

Checking shard version during restore can cause StaleConfig exception propagated for writes incorrectly

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 7.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Sharding EMEA
    • Fully Compatible
    • ALL
    • Sharding EMEA 2023-05-29, Sharding EMEA 2023-06-12, Sharding EMEA 2023-06-26
    • 108

      This is a follow-up investigation for the duplicate time-series inserts issue. Besides SERVER-77063, it seems inserts that don't perform any compression can also result in duplicate measurements when there's a concurrent chunk migration. The logging implied that the write to storage succeeded while a StaleConfig exception was also thrown.

      SERVER-74087 introduced the check of shard version during restore in query stages. This can cause the StaleConfig exception returned incorrectly which can lead to data inconsistencies.

            Assignee:
            jordi.serra-torrens@mongodb.com Jordi Serra Torrens
            Reporter:
            yuhong.zhang@mongodb.com Yuhong Zhang
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated:
              Resolved: