[SERVER-5671] delete and removeRange are logged to the oplog before deleting instead of after Created: 20/Apr/12 Updated: 11/Jul/16 Resolved: 20/May/14 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 2.7.1 |
| Type: | Question | Priority: | Major - P3 |
| Reporter: | Aaron Staple | Assignee: | Greg Studer |
| Resolution: | Done | Votes: | 0 |
| Labels: | cap-ticket-needed | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Description |
|
Most operations are logged after being performed (presumably under the assumption that an assertion occurring during the operation indicates the operation was not applied and should not be logged). However, delete and removeRange seem to be logged to the oplog before being performed. Even if there may not be a complete story in place for logging properly under all error conditions, it may make sense for delete and removeRange to be consistent with other operations. |
| Comments |
| Comment by Ramon Fernandez Marina [ 20/May/14 ] |
|
Author: {u'username': u'gregstuder', u'name': u'Greg Studer', u'email': u'greg@10gen.com'}Message: Branch: master |
| Comment by Greg Studer [ 20/May/14 ] |
|
For whatever reason, this commit doesn't seem to have been caught by the commit hook. Fixed by: https://github.com/mongodb/mongo/commit/9a404af6d545d8e2352342bea6a78b5d675a6950 |
| Comment by Greg Studer [ 07/Mar/14 ] |
|
Still an issue. Looks trivial to fix, putting in 2.7.x. |
| Comment by Eric Milkie [ 07/Mar/14 ] |
|
Still an issue? |