[SERVER-45502] The FCV 4.4 migration protocol does not work on shards with storage engines that do not support document-level locking Created: 10/Jan/20 Updated: 29/Oct/23 Resolved: 15/Jan/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.3 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Esha Maharishi (Inactive) | Assignee: | Esha Maharishi (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: | Sharding 2020-01-27 | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 50 | ||||||||||||
| Description |
|
The FCV 4.4 migration protocol involves doing a retryable write against the recipient shard, and retryable writes are not supported on storage engines that do not have document-level locking. This ticket is to check whether we still support running shard servers on storage engines without document-level locking. If it's not supported, the ticket should figure out what to do about sharding tests that do migrations with the ephemeralForTest storage engine. |
| Comments |
| Comment by Githook User [ 15/Jan/20 ] |
|
Author: {'name': 'Esha Maharishi', 'email': 'esha.maharishi@mongodb.com', 'username': 'EshaMaharishi'}Message: |
| Comment by Esha Maharishi (Inactive) [ 10/Jan/20 ] |
|
Confirmed with alyson1127 that shard servers are required to have a storage engine that supports document-level locking. The only storage engines we claim to support on this public docs page are WiredTiger and inMemory, which both support document-level locking. |