[SERVER-41421] unconditional_step_down.js should check if the storage engine supports document level locking Created: 31/May/19 Updated: 29/Oct/23 Resolved: 04/Jun/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.14 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Pavithra Vetriselvan | Assignee: | Pavithra Vetriselvan |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
unconditional_step_down.js relies on a read and write reaching the "waitInFindBeforeMakingBatch" in a parallel shell. The ephemeral storage engine does not support document level locking, so one of the operations will be blocked behind the other. As suganthi.mani suggested, we should check for document level locking in the test and skip it entirely if the check returns false. |
| Comments |
| Comment by Githook User [ 03/Jun/19 ] |
|
Author: {'name': 'Pavi Vetriselvan', 'email': 'pvselvan@umich.edu', 'username': 'pvselvan'}Message: |