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

Compact command on secondary with nonexistent collection leaves secondary in recovery state

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: 2.0.0
    • Fix Version/s: 2.1.0
    • Component/s: Replication, Storage
    • Labels:
      None
    • Environment:
      Connect to a replica set secondary and try running the compact command on a non-existent collection. You'll get an assertion, and the node will stay in recovery mode.
    • Operating System:
      ALL

      Description

      Connect to a replica set secondary and try running the compact command on a non-existent collection. You'll get an assertion, and the node will move to and remain in a recovery state. You want to node to remain in secondary state, but the only way to fix this is to run compact again on a valid collection.

        Attachments

          Issue Links

          is depended on by

          Bug - A problem which impairs or prevents the functions of the product. SERVER-4329 uncaught exception in mapreduce causes mongod to terminate

          • Major - P3 - Major loss of function.
          • Closed
          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. SERVER-4210 Compact that even failed to start leaves server in "RECOVERING" state

          • Minor - P4 - Minor loss of function, or other problem where easy workaround is present.
          • Closed

            Activity

              People

              Assignee:
              kristina Kristina Chodorow (Inactive)
              Reporter:
              kbanker Kyle Banker
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: