[SERVER-35513] Forbid transactions on inMemory storage engine Created: 08/Jun/18 Updated: 29/Oct/23 Resolved: 14/Jun/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.0.0-rc6, 4.1.1 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Spencer Brody (Inactive) | Assignee: | Tess Avitabile (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||
| Sprint: | Repl 2018-06-18 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
Since rollback to timestamp doesn't work on inMemory, sharded transactions won't work, so we should disable it on replica sets so we have parity between sharded systems and single replica sets, at least until rollback is fixed on inMemory |
| Comments |
| Comment by Githook User [ 14/Jun/18 ] |
|
Author: {'username': 'tessavitabile', 'name': 'Tess Avitabile', 'email': 'tess.avitabile@mongodb.com'}Message: (cherry picked from commit 0b103f9904fe7dfc88d8a1077cf01c30cdd330d0) |
| Comment by Githook User [ 14/Jun/18 ] |
|
Author: {'username': 'tessavitabile', 'name': 'Tess Avitabile', 'email': 'tess.avitabile@mongodb.com'}Message: |