[SERVER-33546] Add numeric syncing field to replSetGetStatus members array Created: 28/Feb/18  Updated: 29/Oct/23  Resolved: 30/Apr/18

Status: Closed
Project: Core Server
Component/s: Diagnostics
Affects Version/s: None
Fix Version/s: 3.4.16, 3.6.6, 4.0.0-rc0

Type: Improvement Priority: Major - P3
Reporter: Bruce Lucas (Inactive) Assignee: Suganthi Mani
Resolution: Fixed Votes: 0
Labels: SWDI, neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
is depended on by SERVER-27230 Poor compression of diagnostic data w... Closed
Documented
is documented by DOCS-11699 Docs for SERVER-33546: Add numeric sy... Closed
Related
is related to SERVER-5461 Add syncSourceHost field to replSetGe... Closed
Backwards Compatibility: Fully Compatible
Backport Requested:
v3.6, v3.4
Sprint: Repl 2018-04-23, Repl 2018-05-07
Participants:

 Description   

An important consideration in debugging issues in the field is which members are syncing from which. It is currently difficult to obtain the history of this and correlate it with other events because this information is currently only available as a string field, which is not preserved as a metric in FTDC.

It would be helpful if the members array had a numeric field which is the _id of the current sync source for that member, or -1 if it has no sync source.

(It is currently possible, but difficult, to obtain this information fro FTDC from the full reference documents stored once per chunk: due to SERVER-27230, when there is a change of sync source typically we also start a new chunk. Once SERVER-27230 is fixed, it will then be impossible to obtain accurate information about changes of sync source from FTDC.)



 Comments   
Comment by Githook User [ 22/May/18 ]

Author:

{'username': 'smani87', 'name': 'Suganthi Mani', 'email': 'suganthi.mani@mongodb.com'}

Message: SERVER-33546 Adding a new field syncSourceId to replSetGetStatus cmd.
SERVER-5461 Adding a new field syncSourceHost to replSetGetStatus cmd.

(cherry picked from commit 649630d10bf6c00225480fe261c042737e5d9688)
Branch: v3.6
https://github.com/mongodb/mongo/commit/4bc31379ea0b218a0cae7d44d78ebb991adf0aba

Comment by Githook User [ 22/May/18 ]

Author:

{'username': 'smani87', 'name': 'Suganthi Mani', 'email': 'suganthi.mani@mongodb.com'}

Message: SERVER-33546 Adding a new field syncSourceId to replSetGetStatus cmd.
SERVER-5461 Adding a new field syncSourceHost to replSetGetStatus cmd.

(cherry picked from commit 649630d10bf6c00225480fe261c042737e5d9688)
Branch: v3.4
https://github.com/mongodb/mongo/commit/f2e995b3b8b6a688c97720e6fdb286e2e538180c

Comment by Githook User [ 27/Apr/18 ]

Author:

{'email': 'suganthi.mani@mongodb.com', 'username': 'smani87', 'name': 'Suganthi Mani'}

Message: SERVER-33546 Adding a new field syncSourceId to replSetGetStatus cmd.
SERVER-5461 Adding a new field syncSourceHost to replSetGetStatus cmd.
Branch: master
https://github.com/mongodb/mongo/commit/649630d10bf6c00225480fe261c042737e5d9688

Comment by Spencer Brody (Inactive) [ 17/Apr/18 ]

Yes, that's right

Comment by Tess Avitabile (Inactive) [ 17/Apr/18 ]

spencer, is the intention that syncSourceId refers to the same node as syncingTo, but syncingTo contains the hostname of sync source, and syncSourceId contains the _id?

Comment by Bruce Lucas (Inactive) [ 01/Mar/18 ]

That would be perfect, thanks.

Comment by Spencer Brody (Inactive) [ 28/Feb/18 ]

We can add a 'syncSourceId' field to the replSetGetStatus output alongside the existing 'syncingTo' field.

Generated at Thu Feb 08 04:33:46 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.