[SERVER-14598] Slaves should handshake all their chained members at once Created: 17/Jul/14 Updated: 14/Apr/16 Resolved: 19/Feb/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | Matt Dannenberg |
| 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 |
|
Currently when a secondary connects to its sync source for upstream position notification, it sends the replSetUpdatePosition command with the "handshake" argument once for itself and once for each member chained off it. After the initial connection, the secondary sends replication progress upstream with a replSetUpdatePosition command that includes information about itself and all chained nodes. We should make handshakes work the same way to avoid multiple network round trips. This may become even more valuable if we raise the max replica set size. |
| Comments |
| Comment by Matt Dannenberg [ 19/Feb/15 ] |
|
handshakes are no longer part of the process of updating replication progress upstream, so this is no longer relevant |
| Comment by Eric Milkie [ 19/Feb/15 ] |
|
Can this be resolved as Gone Away? |