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

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

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 2.1.0
    • Affects Version/s: 2.0.0
    • Component/s: Replication, Storage
    • 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.
    • ALL

      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.

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

              Created:
              Updated:
              Resolved: