[SERVER-28580] Assign replica set heartbeats unique IDs Created: 31/Mar/17 Updated: 06/Dec/22 Resolved: 10/Apr/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | William Schultz (Inactive) | Assignee: | Backlog - Replication Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Replication
|
||||||||
| Participants: | |||||||||
| Description |
|
For introspection and debugging of a replica set system, it can be helpful to correlate heartbeat requests and responses. Currently we have some logging of request ids in the REPL_HB component, but these request ids are really identifiers that should live in the network command layer. It would be nice if we had heartbeat ids at the replication layer that we could attach to all heartbeat requests. Ids that are unique per node would probably suffice, since we can usually determine sender and receiver information of heartbeat messages. |