[SERVER-56887] setIndexCommitQuorum command returns {ok: 1} when run against a mongos on a non-existent index build Created: 12/May/21 Updated: 29/Oct/23 Resolved: 12/Aug/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 5.0.0, 4.4.6 |
| Fix Version/s: | 4.4.11, 5.0.4, 5.1.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Gregory Wlodarek | Assignee: | Haley Connelly |
| 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: |
v5.0, v4.4
|
|||||||||||||||||||||||||
| Steps To Reproduce: |
|
|||||||||||||||||||||||||
| Sprint: | Execution Team 2021-08-09, Execution Team 2021-08-23 | |||||||||||||||||||||||||
| Participants: | ||||||||||||||||||||||||||
| Description |
|
I tried to run setIndexCommitQuorum against a mongos on a non-existent index build and the command returns successfully:
Running the same command against the primary mongod returns the expected result:
|
| Comments |
| Comment by Githook User [ 14/Oct/21 ] |
|
Author: {'name': 'Haley Connelly', 'email': 'haley.connelly@mongodb.com', 'username': 'haleyConnelly'}Message: when run against a mongos on a non-existent index build (cherry picked from commit d0f6a9a599a81e5563c353177a1e7c2df9c21302) |
| Comment by Vivian Ge (Inactive) [ 06/Oct/21 ] |
|
Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you! |
| Comment by Githook User [ 29/Sep/21 ] |
|
Author: {'name': 'Haley Connelly', 'email': 'haley.connelly@mongodb.com', 'username': 'haleyConnelly'}Message: when run against a mongos on a non-existent index build (cherry picked from commit d0f6a9a599a81e5563c353177a1e7c2df9c21302) |
| Comment by Haley Connelly [ 12/Aug/21 ] |
|
The outcome of this ticket: setIndexCommitQuorum on a mongos now broadcasts only to shards that own chunks. Additionally, it reports which shards report success and which failed (if any) along with the standard {ok: <>} response. One thing to note - suppose mongos broadcasts the command to 2 shards: We believe the scenario to be possible but highly unlikely |
| Comment by Githook User [ 12/Aug/21 ] |
|
Author: {'name': 'Haley Connelly', 'email': 'haley.connelly@mongodb.com', 'username': 'haleyConnelly'}Message: when run against a mongos on a non-existent index build |