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

Secondary stuck during index building

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Incomplete
    • Icon: Critical - P2 Critical - P2
    • None
    • 2.4.1
    • None
    • None
    • Linux

    Description

      2.4.1 replica set
      Customer build a index on the primary as background
      The secondary built the index and then got the following error
      DR102 too much data written uncommitted 314.9MB

      After this secondary was at 100% cpu and not reachable by other members.
      I deleted the secondary data and resynced but same issue.
      Then I took the server offline from replica set and deleted the added index. After that the server was fine. The logs are attached from the secondary

      Attachments

        1. mongod.log
          98.48 MB

        Activity

          People

            Unassigned Unassigned
            dharshanr@scalegrid.net Dharshan Rangegowda
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: