[SERVER-26200] Add testing of non-snapshot readAfterOptime Created: 20/Sep/16 Updated: 06/Dec/17 Resolved: 02/Jun/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 3.5.9 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Eric Milkie | Assignee: | Misha Tyulenev |
| Resolution: | Done | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding 2017-06-19 |
| Participants: |
| Description |
|
Currently, the code exists in ReplicationCoordinatorImpl::waitUntilOpTimeForRead() but is unused and untested. We should either exercise that code path in a test or remove the code. |
| Comments |
| Comment by Misha Tyulenev [ 02/Jun/17 ] |
|
The tests are there: https://github.com/mongodb/mongo/blob/3.5/src/mongo/db/repl/replication_coordinator_impl_test.cpp#L3560 |
| Comment by Andy Schwerin [ 21/Sep/16 ] |
|
I vote we test it. This describes read after optime with local read concern, right? That should be tested, I think, rather than removed. |