[SERVER-39482] Fix backup_restore.js to check for WriteCommandError while inserting data to "afterClientKills" collection. Created: 09/Feb/19 Updated: 29/Oct/23 Resolved: 27/Feb/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.9 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Suganthi Mani | Assignee: | Suganthi Mani |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Repl 2019-02-25, Repl 2019-03-11 | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
If, suppose, the primary node steps down before inserting data to "afterClientKills" collection, the insert command fails. Since, currently we don't check for write command error for that insert op, assert.soonNoExcept keeps retrying the insert op for 10 mins without spitting any kind of write command error message. |
| Comments |
| Comment by Githook User [ 27/Feb/19 ] |
|
Author: {'name': 'Suganthi Mani', 'username': 'smani87', 'email': 'suganthi.mani@mongodb.com'}Message: |