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

Invariant that chunk migration is actually reflected in the metadata after successful commit

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.4.17, 3.6.7, 4.0.1, 4.1.2
    • Component/s: Sharding
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Backport Requested:
      v4.0, v3.6, v3.4
    • Sprint:
      Sharding 2018-07-30
    • Linked BF Score:
      15

      Description

      Currently, if for some reason the successfully committed chunk migration is not visible after refresh, the code will silently return a succeeded status. Such situation would be a data corruption and instead we should invariant and output diagnostic information.

        Attachments

          Issue Links

          related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-36232 Refresh after chunk migration commit may not see the committed metadata

          • Critical - P2 - Crashes, loss of data, severe memory leak.
          • Closed

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: