[SERVER-15192] Make all logOp listeners rollback-safe Created: 09/Sep/14 Updated: 21/Jul/17 Resolved: 25/Feb/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 3.0.4, 3.1.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Mathias Stearn | Assignee: | Randolph Tan |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||||||||||||||||||||||||||||||
| Backport Completed: | |||||||||||||||||||||||||||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||||||||||||||||||||||||||
| Description |
|
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. |
| Comments |
| Comment by Githook User [ 21/Jul/17 ] |
|
Author: {u'username': u'andy10gen', u'name': u'Andy Schwerin', u'email': u'schwerin@mongodb.com'}Message: This comment was obsoleted by |
| Comment by Githook User [ 08/Jun/15 ] |
|
Author: {u'username': u'andy10gen', u'name': u'Andy Schwerin', u'email': u'schwerin@mongodb.com'}Message: This rolls up commits with the following summaries from the master development
|
| Comment by Githook User [ 24/Feb/15 ] |
|
Author: {u'username': u'dstorch', u'name': u'David Storch', u'email': u'david.storch@10gen.com'}Message: |
| Comment by Githook User [ 24/Feb/15 ] |
|
Author: {u'username': u'renctan', u'name': u'Randolph Tan', u'email': u'randolph@10gen.com'}Message: Do not perform a query while committing. |
| Comment by Andy Schwerin [ 19/Feb/15 ] |
|
renctan will be fixing the implementation of logOpForSharding
|
| Comment by Githook User [ 18/Feb/15 ] |
|
Author: {u'username': u'alabid', u'name': u'alabid', u'email': u'alabidan@gmail.com'}Message: |
| Comment by Githook User [ 18/Feb/15 ] |
|
Author: {u'username': u'alabid', u'name': u'alabid', u'email': u'alabidan@gmail.com'}Message: |
| Comment by Githook User [ 13/Feb/15 ] |
|
Author: {u'username': u'alabid', u'name': u'alabid', u'email': u'alabidan@gmail.com'}Message: |
| Comment by Githook User [ 13/Feb/15 ] |
|
Author: {u'username': u'alabid', u'name': u'alabid', u'email': u'alabidan@gmail.com'}Message: The initial version of this commit was initially reverted because |
| Comment by Githook User [ 12/Feb/15 ] |
|
Author: {u'username': u'visualzhou', u'name': u'Siyuan Zhou', u'email': u'siyuan.zhou@mongodb.com'}Message: Revert " This reverts commit 295cb7943e21a22f9f3a95006de21b07b254afd2. |
| Comment by Githook User [ 11/Feb/15 ] |
|
Author: {u'username': u'alabid', u'name': u'alabid', u'email': u'alabidan@gmail.com'}Message: |
| Comment by Andy Schwerin [ 06/Feb/15 ] |
|
Proposed solution is for logOpForSharding and AuthorizationManager::logOp to register commit listeners to do their work only on commit, and to only register those listeners when there will be work to do. |
| Comment by Igor Canadi [ 23/Sep/14 ] |
|
Is it expected that RocksDB fails with this error when running jstests/core/apitest_dbcollection.js? |
| Comment by Githook User [ 12/Sep/14 ] |
|
Author: {u'username': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}Message: Since there are currently logOp listeners that are not rollback safe we are |
| Comment by Andy Schwerin [ 09/Sep/14 ] |
|
redbeard0531, if it's convenient, consider doing this in conjunction with |