[SERVER-22148] Move logic to determine if a replica set supports committed reads into a js library Created: 12/Jan/16 Updated: 05/Feb/16 Resolved: 12/Jan/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication, Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 3.3.1 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Charlie Swanson | Assignee: | Charlie Swanson |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Query F (02/01/16) |
| Participants: |
| Description |
|
There are many tests of committed reads that all have to perform a similar check to determine if the test can be run against the current storage engine (e.g. jstests/replsets/read_committed.js and jstests/replsets/read_committed_no_shapshots.js). Not only is the code duplicated, but it's also pretty hard to read. We should move it into a library such as jstests/replsets/rslib.js. |
| Comments |
| Comment by Githook User [ 12/Jan/16 ] |
|
Author: {u'username': u'cswanson310', u'name': u'Charlie Swanson', u'email': u'charlie.swanson@mongodb.com'}Message: Many read committed tests share some fairly complex code to determine |