[SERVER-26169] Place linearizable read support behind a flag Created: 19/Sep/16 Updated: 25/Jan/17 Resolved: 28/Sep/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 3.4.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Andy Schwerin | Assignee: | Benety Goh |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Repl 2016-10-10 | ||||||||
| Participants: | |||||||||
| Description |
|
Linearizable read support should be placed behind a startup-time setParameter flag, defaulting to disabled, until we've finished resolving any outstanding build failures. This will prevent end users from accidentally using the feature before it has passed all of our qualifications. When the flag is set to the disabled state, attempts to use linearizable read concern should return an error with a message clearly indicating that linearizable read support is not enabled. |
| Comments |
| Comment by Githook User [ 14/Oct/16 ] |
|
Author: {u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}Message: Revert " This reverts commit 7f6eb7f2361addf3f75308bf1603caa8cdc71b68. |
| Comment by Githook User [ 28/Sep/16 ] |
|
Author: {u'username': u'benety', u'name': u'Benety Goh', u'email': u'benety@mongodb.com'}Message: |