[SERVER-48059] concurrency_replication_for_backup_restore's WaitForReplication hook should ignore shutdown errors due to quiesce mode Created: 08/May/20 Updated: 29/Oct/23 Resolved: 12/May/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.7.0, 4.4.13 |
| 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 | ||||||||
| Backport Requested: |
v4.4
|
||||||||
| Sprint: | Repl 2020-05-18 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 32 | ||||||||
| Description |
|
backup_restore.js can call rst.stop() while concurrently running the WaitForReplication hook. After the quiesce mode project, we started failing any new and running isMaster requests with ShutdownInProgress errors. This means that when we try to create a new replset test fixture here (while a node is being shut down), the hook will fail with a ShutdownInProgress error. This hook should swallow the errors if we're in quiesce mode. |
| Comments |
| Comment by Githook User [ 11/Feb/22 ] |
|
Author: {'name': 'Pavi Vetriselvan', 'email': 'pvselvan@umich.edu', 'username': 'pvselvan'}Message: (cherry picked from commit 4639620984ecf63486a8c3a2534151d9bc619b9a) |
| Comment by Githook User [ 11/May/20 ] |
|
Author: {'name': 'Pavi Vetriselvan', 'email': 'pvselvan@umich.edu', 'username': 'pvselvan'}Message: |