[SERVER-34704] Write test for transactions on collections that are renamed concurrently Created: 26/Apr/18 Updated: 29/Oct/23 Resolved: 05/Jun/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.0.0-rc5, 4.1.1 |
| Type: | Task | Priority: | Minor - P4 |
| Reporter: | William Schultz (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 | ||||||||||||||||
| Backport Requested: |
v4.0
|
||||||||||||||||
| Sprint: | Repl 2018-05-21, Repl 2018-06-04, Repl 2018-06-18 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Story Points: | 1 | ||||||||||||||||
| Description |
|
We want to test the interaction of transactions and collection renames. We should test cases where a transactions writes to a collection A that is concurrently renamed to B. We should verify the renameCollection blocks until the transaction commits or until maxTimeMS expires. We should test this when A and B are in the same database and when they are in different databases. |
| Comments |
| Comment by Githook User [ 05/Jun/18 ] |
|
Author: {'username': 'tessavitabile', 'name': 'Tess Avitabile', 'email': 'tess.avitabile@mongodb.com'}Message: (cherry picked from commit 14ffe1360e095d98da824bb63417672f3b171270) |
| Comment by Githook User [ 05/Jun/18 ] |
|
Author: {'username': 'tessavitabile', 'name': 'Tess Avitabile', 'email': 'tess.avitabile@mongodb.com'}Message: |