[SERVER-29348] Range deletion write majority failure not propagated Created: 24/May/17 Updated: 30/Oct/23 Resolved: 25/May/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.5.5 |
| Fix Version/s: | 3.5.8 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Nathan Myers | Assignee: | Nathan Myers |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Steps To Reproduce: | Examination of db/s/collection_range_deleter.cpp: it logs the failure, but does not notify listeners. |
| Sprint: | Sharding 2017-05-29 |
| Participants: |
| Description |
|
Esha has noticed that a failure when waiting for write majority on deleting a range is not passed on to listeners for the results of the operation. |
| Comments |
| Comment by Githook User [ 24/May/17 ] |
|
Author: {u'username': u'ncm', u'name': u'Nathan Myers', u'email': u'ncm@cantrip.org'}Message: |