[SERVER-16824] Run isSelf concurrently for all members Created: 13/Jan/15 Updated: 30/Jan/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Scott Hernandez (Inactive) | Assignee: | Backlog - Replication Team |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Replication
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
Currently we sequentially run isSelf and create network connections if needed when we really want to do this in parallel. Since the network timeout is 30 seconds this could take up to N (member) * 30 seconds to complete. |
| Comments |
| Comment by Opal Hoyt [ 30/Jan/23 ] |
|
Backlogging this in favor of BACKPORT-14562 |
| Comment by Opal Hoyt [ 23/Jan/23 ] |
|
Leaving this in triage while we investigate https://jira.mongodb.org/browse/SERVER-72980 |