[SERVER-27934] Config Server Optime difference from rs.status() output Created: 07/Feb/17 Updated: 26/Apr/19 Resolved: 16/Feb/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 3.2.11 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Wei Shan Ang | Assignee: | Kelsey Schubert |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
FreeBSD 11 64bit, MongoDB 3.2.11 |
||
| Attachments: |
|
| Backwards Compatibility: | Minor Change |
| Operating System: | ALL |
| Steps To Reproduce: | 1. Deploy config server in CSRS. |
| Participants: |
| Description |
|
Hi all! I think I found a bug when querying for config server optime via replSetGetStatus command somehow.
If you see the above, the optime on the primary is 1486474501, which is the actual last entry in the oplog. However, when I query the config server using replSetGetStatus (pymongo), it shows the uptime instead.
This only happens on CSRS config server replica sets. Thanks! |
| Comments |
| Comment by Ian Whalen (Inactive) [ 26/Apr/19 ] | ||
|
Switching "Drivers Changes Needed" from "Maybe" to "Not Needed" since this was closed as something other than Fixed. | ||
| Comment by Kelsey Schubert [ 16/Feb/17 ] | ||
|
Hi weishan, Thanks for the additional information. From your responses, I do not see anything to indicate a bug in the MongoDB server. If another write was performed, it is expected that the optime would change between calls to rs.status(). If you would like us to continue to investigate, would you please a reproduction that guarantees that the optime should be the same? For MongoDB-related support discussion please post on the mongodb-user group or Stack Overflow with the mongodb tag. A question like this involving more discussion would be best posted on the mongodb-users group. Users there may be able to help explain this behavior or guide you to construct a reproduction to help our investigation. Thank you, | ||
| Comment by Wei Shan Ang [ 08/Feb/17 ] | ||
|
Hi Mark, I have just reattach the output again to show the issue better. Yesterday, I did a failover as we were doing some maintenance. After that, I found out the issue has reversed. Now, the optime of rs.status() output is valid but the output in replSetGetStatus stays the same. | ||
| Comment by Mark Agarunov [ 07/Feb/17 ] | ||
|
Hello weishan, Thank you for the report. Looking over the output you've provided, I don't seem to see the behavior you're describing. With rs.status() the optime is showing:
And in the pymongo/replSetGetStatus output it's showing:
which is only a few seconds after the optime from the mongo shell. The output of both appears to be the same; both show uptime and optime. If I am misunderstanding the issue you are describing, please let me know and we'll continue debugging. Thanks, |