[SERVER-35224] snapshot_cursor_shutdown_stepdown.js should not perform transactions on secondaries Created: 25/May/18 Updated: 29/Oct/23 Resolved: 25/May/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.0.0-rc1, 4.1.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Tess Avitabile (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 | ||||||||
| Operating System: | ALL | ||||||||
| Backport Requested: |
v4.0
|
||||||||
| Sprint: | Repl 2018-06-04 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 0 | ||||||||
| Description |
|
This test triggers a stepdown that aborts a transaction, then checks that the cursor opened in the transaction was killed. It does so by running a getMore on that cursor in a transaction and checking for the CursorNotFound error code. There is no reason that the getMore needs to be done in a transaction, and this transaction occasionally aborts while trying to acquire the global lock. Since read-only transactions are not yet supported on secondaries, we should address the test failure by not running the getMore in a transaction. |
| Comments |
| Comment by Githook User [ 25/May/18 ] |
|
Author: {'username': 'tessavitabile', 'name': 'Tess Avitabile', 'email': 'tess.avitabile@mongodb.com'}Message: (cherry picked from commit 8b91c95e7f39be8d90f5bf631ee256fa6b3c31f4) |
| Comment by Githook User [ 25/May/18 ] |
|
Author: {'username': 'tessavitabile', 'name': 'Tess Avitabile', 'email': 'tess.avitabile@mongodb.com'}Message: |