[SERVER-46625] Improve diagnostics when mongocryptd requests are sent to non-mongocryptd daemon Created: 04/Mar/20 Updated: 29/Oct/23 Resolved: 02/Jun/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 4.2.1 |
| Fix Version/s: | 4.7.0, 4.4.2, 4.2.11 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Oleg Pudeyev (Inactive) | Assignee: | Katherine Wu (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | qopt-team | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Backport Requested: |
v4.4, v4.2
|
||||||||||||||||
| Sprint: | Query 2020-04-20, Query 2020-05-04, Query 2020-05-18, Query 2020-06-01, Query 2020-06-15 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
The default port of mongocryptd is 27020. The default port of mongod is 27017. There is precedent (for example, mlaunch does this, as well as drivers' test suites in evergreen) to start launching mongod/mongos on 27017 and go up in port numbers until the required number of daemons is provisioned. Following the described port allocation for mongod/mongos processes, eventually there is going to be a mongod or mongos on port 27020. When this happens, operations fail with the following cryptic error:
Note that the above exception is referencing localhost:27019. Here is what happened:
Expected behavior: As a user of the driver, when the driver sends a command intended for mongocryptd to a mongod/mongos I want to be informed that the command was received by the wrong process, so that I can immediately take corrective action (reconfigure the driver and/or my deployments). Actual behavior: The error message produced does not indicate the root cause of the problem (command received by wrong daemon). |
| Comments |
| Comment by Githook User [ 30/Sep/20 ] |
|
Author: {'name': 'Katherine Wu', 'email': 'katherine.wu@mongodb.com', 'username': 'kaywux'}Message: (cherry picked from commit becc8e5ecca4260e844725fa71f4ed1164647e4a) |
| Comment by Githook User [ 11/Sep/20 ] |
|
Author: {'name': 'Katherine Wu', 'email': 'katherine.wu@mongodb.com', 'username': 'kaywux'}Message: (cherry picked from commit becc8e5ecca4260e844725fa71f4ed1164647e4a) |
| Comment by Githook User [ 02/Jun/20 ] |
|
Author: {'name': 'Katherine Wu', 'email': 'katherine.wu@mongodb.com', 'username': 'kaywux'}Message: |
| Comment by Githook User [ 01/Jun/20 ] |
|
Author: {'name': 'Katherine Wu', 'email': 'katherine.wu@mongodb.com', 'username': 'kaywux'}Message: Revert " This reverts commit 60124ec2ef0acf2e6747d620779cc40c9376c9b6. |
| Comment by Githook User [ 01/Jun/20 ] |
|
Author: {'name': 'Katherine Wu', 'email': 'katherine.wu@mongodb.com', 'username': 'kaywux'}Message: |
| Comment by David Storch [ 23/Mar/20 ] |
|
Sending to the QO team for triage. |
| Comment by Mark Benvenuto [ 20/Mar/20 ] |
|
Assigning to query team to investigate since this error is coming when a user does an insert. While the IDL parser is the one throwing this error, we could build a special case into IDL for this field in this case. |