[SERVER-42850] asCluster() can receive incorrect _liveNodes value due to transient network issues Created: 16/Aug/19 Updated: 23/Sep/19 Resolved: 23/Sep/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Pavithra Vetriselvan | Assignee: | Pavithra Vetriselvan |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Operating System: | ALL | ||||
| Sprint: | Repl 2019-08-26, Repl 2019-09-09, Repl 2019-09-23, Repl 2019-10-07 | ||||
| Participants: | |||||
| Linked BF Score: | 30 | ||||
| Description |
|
In replsettest.js, if a transient network error occurs during _callIsMaster(), the node that failed to connect will not get added to _liveNodes. When we stop a replica set and do our auth checks, it is possible to pass _liveNodes into asCluster() without the correct number of live nodes. We should make sure that _liveNodes isn't missing a node before we send it through asCluster(). |
| Comments |
| Comment by Pavithra Vetriselvan [ 06/Sep/19 ] |
|
Code review URL: http://mongodbcr.appspot.com/485320003 |