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

Mongo fail-over primary take some time.

    • Type: Icon: Bug Bug
    • Resolution: Incomplete
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 3.6.17
    • Component/s: None
    • Labels:
      None
    • ALL

      Hi Team,

      When I reboot mongo01 node its going to take primary as mongo02 node. After rebooted the mongo01 node get back to primary with STARTUP state. After sometime(20 ms ) moved to PRIMARY state. Please suggest me, why this was happened on my machine. 

      Previously it didn't happened like that. 

       

      2020-07-29T14:51:50.696+0530 I REPL [replexec-244] Member mongo01:27717 is now in state STARTUP

      2020-07-29T14:52:10.703+0530 I REPL [replexec-249] Member mongo01:27717 is now in state PRIMARY

       

      2020-07-29T14:51:52.803+0530 I REPL [replication-1] ******
      2020-07-29T14:51:52.803+0530 I STORAGE [replication-1] dropAllDatabasesExceptLocal 1
      2020-07-29T14:51:52.803+0530 I ASIO [NetworkInterfaceASIO-RS-0] Connecting to mongo02:27717
      2020-07-29T14:51:52.804+0530 I ASIO [NetworkInterfaceASIO-RS-0] Successfully connected to mongo02:27717, took 1ms (1 connections now open to mongo02:27717)
      2020-07-29T14:51:52.805+0530 I ASIO [NetworkInterfaceASIO-RS-0] Connecting to mongo02:27717
      2020-07-29T14:51:52.821+0530 I ASIO [NetworkInterfaceASIO-RS-0] Successfully connected to mongo02:27717, took 16ms (2 connections now open to mongo02:27717)
      2020-07-29T14:51:52.827+0530 I REPL [replication-1] CollectionCloner::start called, on ns:admin.system.users

       

      Thanks,

      Vasanth

            Assignee:
            dmitry.agranat@mongodb.com Dmitry Agranat
            Reporter:
            vasanth3g@gmail.com Vasanth M.Vasanth
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: