Fix multiVersion test failure seen with new unique indexes on binary downgrade

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Gone away
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Storage
    • ALL
    • Storage Non-NYC 2018-07-16, Storage Engines 2018-07-30
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      The test global_snapshot_reads_downgrade_cluster.js fails when timestamp safe unique indexes are enabled.

      [js_test:global_snapshot_reads_downgrade_cluster] 2018-04-30T13:35:16.169+0000 c20277| 2018-04-30T13:35:16.169+0000 F -        [initandlisten] Fatal assertion 28579 UnsupportedFormat: Application metadata for table:index-17--7382423157972859957 has unsupported format version: 10. Index: {name: ns_1_min_1, ns: config.chunks} - version too new for this mongod. See http://dochub.mongodb.org/core/3.4-index-downgrade for detailed instructions on how to handle this error. at src/mongo/db/storage/wiredtiger/wiredtiger_index.cpp 268

      It seems that it is required to recreate unique indexes in this test before binary downgrade.

              Assignee:
              Vamsi Boyapati
              Reporter:
              Neha Khatri (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: