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

Different Uptimes shown in rs.status() across diferent network locations when there are latency issyes



    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Admin
    • Labels:
    • Operating System:



      Hi Team,

      we have 6 nodes replica set
      1. 3 nodes in one geographic location say Location 1 .
      2. 3 other non votable members different geographic location for the purpose of Disaster Recovery say Location 2.


      Whenever there was a network glitch or latency between these geographic locations , we see that the DR nodes on Location 2 are unable to reach the other 3 nodes on Location 1 and vice versa from the logs
      saying "unable to reach the host ip address / time out" .


      The problem is
      1. when we do rs.status () from the Node 1 , Primary from Location 1 , it shows the "up times" of all the DR nodes on Location 2 say 1600s.

      2. when we do rs.status () from the Node 4 , secondary from Location 2 , it shows the "up times" of all the Primary nodes on Location 1 say 1600s.

      Actually all the nodes are up and running more than a year with out any downtime. The Question is why the "UPTIMES" is shown different , when rs.status is evaluated from 2 different geo locations , when none of the nodes are down.

      Please suggest and request to help us to understand why we see this difference in UPTIMES..





            • Votes:
              0 Vote for this issue
              6 Start watching this issue


              • Created: