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

Index builder can skip index building for a non-empty collections due to incorrect fast count value.

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 4.3.4
    • Storage
    • None
    • Fully Compatible
    • ALL
    • Execution Team 2020-01-27, Execution Team 2020-02-10
    • 86

    Description

      Currently the fast count gets flushed to WT/disk only during following cases.
      1) fsync
      2) clean shutdown.
      3) During releasing WT session at an interval of 60 seconds (default) or 1000 ticks.
      4) During recovering to stable timestamp

      Basically, fast count is not tolerant to unclean shutdowns. So, if a node containing non-empty collections restarts after an unclean shutdown, there is  a possibility that that fast count returned after node restart can be 0 for that non-empty collection. As, a result, index build can skip index building thinking that's an empty collection.

      Attachments

        Issue Links

          Activity

            People

              suganthi.mani@mongodb.com Suganthi Mani
              suganthi.mani@mongodb.com Suganthi Mani
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: