[SERVER-34379] Primary is -1 Sec behind the primary Created: 09/Apr/18 Updated: 27/Oct/23 Resolved: 10/Apr/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Anand Mohan | Assignee: | Kelsey Schubert |
| Resolution: | Works as Designed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
Hi , In my environment , Secondary is -1 Sec behind the primary. This is an intermittent issue.
Please help me in resolve this issue |
| Comments |
| Comment by Kelsey Schubert [ 10/Apr/18 ] |
|
Sorry, I'm not sure how I missed that on my first read. In our documentation, we clarify that negative values may be expected in certain cases when run against a secondary. If you're curious, I wrote up an detailed example of how/why this might occur in Kind regards, |
| Comment by Anand Mohan [ 10/Apr/18 ] |
|
Hi Kelsey, i am executing this in Secondary as you can see in the output which i updated earlier. |
| Comment by Kelsey Schubert [ 09/Apr/18 ] |
|
Would you please clarify whether you are executing rs.printSlaveReplicationInfo() on the primary or secondary? Thank you, |
| Comment by Anand Mohan [ 09/Apr/18 ] |
|
Hi Fernandez, I checked the timing but it is in sync. MongoDB Enterprise rs01:PRIMARY> Date() MongoDB Enterprise rs01:SECONDARY> Date() |
| Comment by Ramon Fernandez Marina [ 09/Apr/18 ] |
|
gg.anands@gmail.com, what version of MongoDB are you using? A simple explanation for this could be that your nodes are not properly time-synchronized – can you please check whether there's a time difference between the clocks of the affected nodes and report back? Thanks, |