[SERVER-24570] fix overeager dassert in WriteConcernResult::appendTo Created: 14/Jun/16 Updated: 05/Jul/16 Resolved: 15/Jun/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | 3.3.8 |
| Fix Version/s: | 3.3.9 |
| Type: | Bug | Priority: | Trivial - P5 |
| Reporter: | Geert Bosch | Assignee: | Geert Bosch |
| Resolution: | Done | 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 | ||||
| Steps To Reproduce: | Run dropdb_race.js on a server compiled with --dbg=on and the inMemory storage engine. |
||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
There is a check in WriteConcernResult::appendTo that checks that either a positive number of files was fsync-ed, or a "waited" field is added. However, for ephemeral storage engines, it is OK to have 0 files synched. |
| Comments |
| Comment by Githook User [ 15/Jun/16 ] |
|
Author: {u'username': u'GeertBosch', u'name': u'Geert Bosch', u'email': u'geert@mongodb.com'}Message: |