[SERVER-15929] Verify rollback files are written without errors Created: 03/Nov/14 Updated: 25/Jan/17 Resolved: 25/Sep/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 3.1.9 |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Angshuman Bagchi (Inactive) | Assignee: | Benety Goh |
| Resolution: | Done | Votes: | 0 |
| Labels: | rollback | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Sprint: | RPL A (10/09/15) | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
When writing rollback files, the status of the rollback file creation is checked and if it fails, the operation is aborted. However, the return status of the write call is not checked. So it's possible that if the disk were full or otherwise unavailable, errors would be masked. |
| Comments |
| Comment by Githook User [ 25/Sep/15 ] |
|
Author: {u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}Message: |
| Comment by Githook User [ 25/Sep/15 ] |
|
Author: {u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}Message: |
| Comment by Githook User [ 25/Sep/15 ] |
|
Author: {u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}Message: |