[SERVER-47043] Read concern set to default when it should be local Created: 23/Mar/20 Updated: 29/Oct/23 Resolved: 24/Mar/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication, Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.4.0-rc0, 4.3.6, 4.7.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Marcos José Grillo Ramirez | Assignee: | Marcos José Grillo Ramirez |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | sharding-4.4-stabilization | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||
| Backport Requested: |
v4.4
|
||||||||||||||||||||
| Sprint: | Sharding 2020-04-06 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
The replication subsystem should always want to do local read concern on the oplog (with the exception of change streams), however, we've detected at least two points where is set to default:
This issue can be seen clearly if the read and write concern defaults are set after the logical session cache refresh on a replica set. Investigate on these points and if there are others that should also be local. |
| Comments |
| Comment by Githook User [ 26/Mar/20 ] |
|
Author: {'name': 'Kevin Pulo', 'username': 'devkev', 'email': 'kevin.pulo@mongodb.com'}Message: (cherry picked from commit 747ff353cbc819d032fa727d4bd7ffad16ea0437)
(cherry picked from commit 165b01c12f72840a25f16e1fe9b9b4df4bffa3ea)
(cherry picked from commit ad5a5fd53f50a0290338ea701489f3c18f1fa308) |
| Comment by Githook User [ 24/Mar/20 ] |
|
Author: {'email': 'kaloian.manassiev@mongodb.com', 'name': 'Kaloian Manassiev', 'username': 'kaloianm'}Message: Revert " This reverts commit 81c6113198d2f5debf3da38a42bf61d7a079de2e. We discovered that this commit introduces |
| Comment by Githook User [ 24/Mar/20 ] |
|
Author: {'email': 'marcos.grillo@mongodb.com', 'name': 'Marcos José Grillo Ramírez', 'username': 'm4nti5'}Message: |