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

Index build external sort files can collide with existing external sort files for resumed index builds

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.8.0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • Execution Team 2020-10-05

      Say a resumable index build with external sort file extsort-index.0 is interrupted for shutdown during the collection scan or bulk load phases and then resumed on startup. The resumed index build will continue to use the same external sort file. However, now consider a new index build started while the resumed index build is still in progress. This new index build will attempt to also use an external sort file named extsort-index.0 due to the filename counter starting back at 0.

      Another scenario is if the resume info failed to parse on startup, the external sort file extsort-index.0 will become orphaned until a subsequent restart without any index builds to resume (or an unclean shutdown). The external sort files can then collide in the same way as described above.

            Assignee:
            gregory.noma@mongodb.com Gregory Noma
            Reporter:
            gregory.noma@mongodb.com Gregory Noma
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: