Uploaded image for project: 'WiredTiger'
  1. WiredTiger
  2. WT-8597

Understand why version 4.4.2 of MongoDB isn't susceptible to data loss on upgrade

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Works as Designed
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage - Ra 2022-01-10
    • 5

      In WT-8395 we identified a case where an upgrade from versions 4.4.2, 4.4.3 or 4.4.4 to newer releases of MongoDB could cause recovery to remove content that should be durable. See WT-8395 for more context.

      In doing testing, we can reliably reproduce a failure if starting with versions 4.4.3 or 4.4.4, but not 4.4.2.

      Use this ticket to track the investigation of why the issue didn't reproduce with upgrade from version 4.4.2.

        1. log_4.4.2_WT-6816.txt
          6.42 MB
        2. log_4.4.2.txt
          10 kB
        3. log_verbose_4.4.2_WT-6816.txt
          8.67 MB
        4. log_verbose_4.4.2.txt
          11 kB
        5. WT_TEST_4.4.2_WT-6816.tar.gz
          7.57 MB
        6. WT_TEST_4.4.2.tar.gz
          6.78 MB

            Assignee:
            haribabu.kommi@mongodb.com Haribabu Kommi
            Reporter:
            alexander.gorrod@mongodb.com Alexander Gorrod
            Alexey Anisimov (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            11 Start watching this issue

              Created:
              Updated:
              Resolved: