Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Done
Priority: Major - P3
Fix Version/s: 3.0.4, 3.1.0
Affects Version/s: None
Component/s: Storage
Labels:
None

Backwards Compatibility:
Fully Compatible
Backport Completed:

3.0.4

For now I'll make it a fatal error to rollback once you got to logOp, since today, once you get there, you shouldn't need to rollback.

We will want to fix the listeners soon since the plan is that rollbacks will be able to happen at any time, but that can happen outside of the critical path of enabling rollback. The tricky listeners will be the role-graph adjuster and the sharding tracker of deletes for migrations.

is depended on by

SERVER-17250 logOp rollback when legacy insert creates a namespace and then fails to insert the document (fatal assertion)

Closed

is duplicated by

SERVER-17265 thread convoys from WiredTigerRecoveryUnit::registerChange

Closed

is related to

SERVER-18822 Sharded clusters with WiredTiger primaries may lose writes during chunk migration

Closed

SERVER-30240 remove incorrect paragraph from getNextOpTime() comments in oplog.cpp

Closed

related to

SERVER-15774 findAndModify triggers rollback invariant failure with --notablescan

Closed

SERVER-16322 Make sure that RecoveryUnit::commit() can safely throw WriteConflictException

Closed

SERVER-17303 concurrent findAndModify ops with upsert: true can cause a fatal logOp() rollback

Closed

SERVER-17198 logOp rollback in findAndModify when query for modified document fails (fatal assertion)

Closed

SERVER-13896 Replace logOp() with a more operation-aware observer interface

Closed

(4 related to)

Assignee:: Randolph Tan

Reporter:: Mathias Stearn

Participants:: Andy Schwerin, Githook User, Igor Canadi, Mathias Stearn, Randolph Tan

Votes:: 0 Vote for this issue

Watchers:: 13 Start watching this issue

Created:: Sep 09 2014 07:31:36 PM UTC

Updated:: Jul 21 2017 12:44:32 PM UTC

Resolved:: Feb 25 2015 06:37:15 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates