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

MongoDB becomes really slow after changes on Replica Set

    • Type: Icon: Bug Bug
    • Resolution: Incomplete
    • Priority: Icon: Critical - P2 Critical - P2
    • None
    • Affects Version/s: 3.2.1
    • Component/s: Admin, Replication
    • Labels:
      None
    • ALL
    • Hide

      I'm not sure, but I think that having an unavailable member causes some extra load on the primary server, causing a huge decrease on the performance of the server

      Show
      I'm not sure, but I think that having an unavailable member causes some extra load on the primary server, causing a huge decrease on the performance of the server

      I have the following Replica Set

      Server/Member 1 - Primary
      Server/Member 2 - Secondary (can become primary)
      Server/Member 3 - Secondary (cannot become primary, just using for backup purposes)
      Arbiter 1 - not in Replica Set, I just use it sometimes when I need to remove one of the members from the replica set

      After my primary member crashed (bug reported: SERVER-22617), I needed to shutdown member 3 to copy all files and restore my primary server without an initial sync (the oplog window wasn't enough, the server stood down for 12h+).

      I followed this steps:

      • remove member 1 from replica set (member 2 was the primary server for the past 12 hours)
      • add arbiter 1 to the replica set
      • shutdown member 3

      After 1 or 2 minutes, my primary server became REALLY slow, I started member 3 and it didn't fix the slowness. I waited for 5 minutes after starting the member 3 to the replica to check if it was going to become normal again, but only after restarting the service (member 2 - primary) it fixed the slowness.

      If you need any logs or information, I'll be happy to upload it for you, if possible on a private location

            Assignee:
            Unassigned Unassigned
            Reporter:
            ricardo_fanatee Ricardo Hilsenrath
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: