[SERVER-20199] Create a read majority jstest passthrough Created: 25/Aug/15 Updated: 07/Oct/15 Resolved: 21/Sep/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication, Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 3.1.9 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Michael Grundy | Assignee: | Michael Grundy |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Minor Change | ||||||||
| Sprint: | TIG 9 (09/18/15) | ||||||||
| Participants: | |||||||||
| Description |
|
Create a read committed jstest passthrough for the core jstest suite (based on Max's work and the sharding passthrough). Failovers during test runs won't be necessary, majority reads and writes should be enough to exercise the new code. A single node replica set may be enough as well. |
| Comments |
| Comment by Githook User [ 16/Sep/15 ] |
|
Author: {u'username': u'mgrundy', u'name': u'Mike Grundy', u'email': u'michael.grundy@10gen.com'}Message: |
| Comment by Max Hirschhorn [ 25/Aug/15 ] |
|
Attaching PoC for overriding the prototypes in the mongo shell and using existing tests to exercise read committed. The idea comes from kamran.khan to do write operations with a majority write concern and do read operations with a majority read concern while periodically stepping down the primary and electing a new secondary. |