[SERVER-37396] make rollback_auth.js more robust Created: 28/Sep/18 Updated: 29/Oct/23 Resolved: 30/Oct/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | Needs Triage |
| Fix Version/s: | 3.6.9 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Pavithra Vetriselvan | Assignee: | Pavithra Vetriselvan |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Repl 2018-10-08, Repl 2018-10-22, Repl 2018-11-05 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 19 | ||||||||
| Description |
|
rollback_auth.js relies on nodes successfully completing rollback before performing auth checks and currently uses awaitReplication() to do so. Unfortunately, awaitReplication() does not guarantee that a node has rolled back especially in the case of network failures. We should explicitly check the state of the recovering node and make sure it is a secondary before performing these checks. |
| Comments |
| Comment by Githook User [ 30/Oct/18 ] |
|
Author: {'name': 'Pavi Vetriselvan', 'email': 'pvselvan@umich.edu', 'username': 'pvselvan'}Message: |