[SERVER-48489] [SBE] Implement a check that the current node can serve reads Created: 29/May/20 Updated: 29/Oct/23 Resolved: 18/Aug/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.7.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Anton Korshunov | Assignee: | Eric Cox (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: | Query 2020-07-13, Query 2020-07-27, Query 2020-08-10, Query 2020-08-24 | ||||||||
| Participants: | |||||||||
| Description |
|
We have a check in DocumentSourceCursor to ensure that the current node in a replica set can serve reads. Due to the fact that in SBE we use an internal lock policy, we changed this check to only perform it when the lock policy is external, since in DocumentSourceCursor we acquire a collection lock ourselves. That means that in SBE we do not perform this check any longer, so we have to figure out who is going to perform this check in SBE and implement it. |
| Comments |
| Comment by Githook User [ 18/Aug/20 ] |
|
Author: {'name': 'Eric Cox', 'email': 'eric.cox@mongodb.com', 'username': 'ericox'}Message: |
| Comment by Eric Cox (Inactive) [ 18/Aug/20 ] |
|
The above code review was abandoned and this approach was the final work that will be committed into master. Code review: https://mongodbcr.appspot.com/646720001/ |
| Comment by Eric Cox (Inactive) [ 03/Aug/20 ] |
|
Code review: https://mongodbcr.appspot.com/633340006/ |