Can't get in to Mongo Shell for primary node, it hangs, apps could not connect to it

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Cannot Reproduce
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Logging, Networking, Replication
    • None
    • ALL
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      We are running MongoDB 3.2.12 three replica set on dockers on Redhat Linux 4.1.12-61.1.25.el7uek.x86_64. It has happened a few times recently that our apps all a sudden could not connect to the set any more (mark this #1 for reference). I went on the primary node, and could not get into mongo shell to the primary, I could still get in to the two secondaries. And the replication seems still fine (I checked with db.printSlaveReplicationInfo()).

      One other strange thing I noticed is the MongoDB log file stopped being updated on the primary (mark this #2 for reference). It was fine on secondaries. This does not seem to be directly related with the above main issue. It could take days for #1 to happen after #2 happened from recent observations.

      Could you help? We are at a loss and don't know what to look for.

      Thanks,

      Erin

        1. node3_logAug24.txt
          944 kB
        2. node1_logAug24.txt
          569 kB
        3. newdiagAug24.tgz
          99.55 MB
        4. forjira-node3.tgz
          95.62 MB
        5. forjira-node2.tgz
          98.35 MB
        6. forjira-node1.tgz
          98.88 MB

            Assignee:
            Mark Agarunov (Inactive)
            Reporter:
            Erin Bao
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: