[SERVER-14702] ReplSetGetStatus show syncingTo for self in members array Created: 27/Jul/14 Updated: 27/Oct/15 Resolved: 17/Oct/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | 2.7.4 |
| Fix Version/s: | 2.7.8 |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Kevin Pulo | Assignee: | Scott Hernandez (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
The code for self:true in the members array of ReplSetGetStatus shows fewer fields than for remote hosts. Most of these are related to network (like pingMs) or remoteness (like the heartbeat fields), and so don't make sense to show for self. However, when running ReplSetGetStatus on a secondary, it still makes sense to see the syncingTo field, since the secondary is still syncing to some other member, and so it is confusing for the field to be absent. It is easy to miss the top-level syncingTo field when focussing on the status of the members. |
| Comments |
| Comment by Githook User [ 17/Oct/14 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||
|
Author: {u'username': u'scotthernandez', u'name': u'Scott Hernandez', u'email': u'scotthernandez@gmail.com'}Message: | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Eric Milkie [ 12/Sep/14 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||
|
scotthernandez can you check if this behavior is now present in master? | ||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Kevin Pulo [ 29/Jul/14 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||
|
Thanks Scott. Yes, as you suspected, this is about having the information present in the members array, alongside the other hosts which have it. It is easy to miss it at the top level, because the focus is usually on the status of the members. Something like this:
| ||||||||||||||||||||||||||||||||||||||||||||||||||
| Comment by Scott Hernandez (Inactive) [ 27/Jul/14 ] | ||||||||||||||||||||||||||||||||||||||||||||||||||
|
This information is currently provided at the top level, and is not duplicated under the specific member element:
If you want it duplicated within the member please make that clear when you change the description and reopen, or create a new issue. FYI: If the node has no sync source, or if it is shunned/primary no field will be included in the output. Also, in the future please provide an example of the output you expect so it is clear what is being requested, and in what way. |