[SERVER-71523] changeStreams validator fails only on shard servers in some cases Created: 21/Nov/22 Updated: 29/Oct/23 Resolved: 30/Nov/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.3.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Gabriel Marks | Assignee: | Rishab Joshi (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 | ||||||||
| Operating System: | ALL | ||||||||
| Backport Requested: |
v6.2
|
||||||||
| Sprint: | QE 2022-11-28, QE 2022-12-12 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 16 | ||||||||
| Description |
|
Currently, if a cluster parameter validator succeeds on the config server, we expect that cluster parameter's validate and set to always (eventually) succeed on the shard servers. This check: https://github.com/10gen/mongo/blob/91a1e1241f015e592b1e1f7838230cec88b25740/src/mongo/db/change_streams_cluster_parameter.cpp#L45-L50 violates that. We are soon going to change the behavior of sharded cluster setParameter to validate ONLY on the config server to avoid issues like this in the future. |
| Comments |
| Comment by Githook User [ 30/Nov/22 ] |
|
Author: {'name': 'Rishab Joshi', 'email': 'rishab.joshi@mongodb.com', 'username': 'rishvin'}Message: |