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

ensureIndex failure reports ok: 1 on some failures

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: 2.6.0, 2.6.1
    • Fix Version/s: 2.6.5, 2.7.2
    • Component/s: Indexing, Shell
    • Labels:
    • Operating System:
      ALL
    • Backport Completed:
    • Steps To Reproduce:
      Hide

      1) Run mongod against attached datafiles
      2) Try to ensure an index on test.test

      Show
      1) Run mongod against attached datafiles 2) Try to ensure an index on test.test

      Description

      Against a corrupted data set (next extent header pointing to invalid location):

      > db.test.ensureIndex({a:1})
      {
              "createdCollectionAutomatically" : false,
              "numIndexesBefore" : 1,
              "numIndexesAfter" : 1,
              "ok" : 1
      }
      > db.test.ensureIndex({b:1})
      {
              "createdCollectionAutomatically" : false,
              "numIndexesBefore" : 1,
              "numIndexesAfter" : 1,
              "ok" : 1
      }
      > 

      Seems like ok should not be set to 1 here

        Attachments

        1. corrupttest.tgz
          125.19 MB
          Andrew Emil

          Activity

            People

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

              Dates

              • Created:
                Updated:
                Resolved: