[SERVER-30550] Test that safe secondary reads is inactive until 3.6 feature compatibility version is set Created: 08/Aug/17 Updated: 30/Oct/23 Resolved: 29/Sep/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.6.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Dianna Hohensee (Inactive) | Assignee: | Dianna Hohensee (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 2017-10-02 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
Test that a 3.4 feature compatibility version mixed shard replica sets behave as v3.4 servers, then smoothly transition to 3.6 feature compatibility operation. In 3.4 fcv, orphans should be readable on secondaries. Once 3.6 fcv is set, secondaries should not need to refresh remotely, but should just start working. The profiler might be useful for testing: https://github.com/mongodb/mongo/blob/master/jstests/libs/profiler.js |
| Comments |
| Comment by Githook User [ 25/Sep/17 ] |
|
Author: {'email': 'dianna.hohensee@10gen.com', 'name': 'Dianna Hohensee', 'username': 'DiannaHohensee'}Message: |
| Comment by Dianna Hohensee (Inactive) [ 08/Aug/17 ] |
|
Should be done after |