[SERVER-28253] MongoDB server configuration does not supersede client driver config Created: 08/Mar/17 Updated: 23/Feb/23 Resolved: 24/Feb/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Admin |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Amine Sahraoui | Assignee: | Backlog - Service Architecture |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | re-triaged-ticket | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
mongodb 3.x |
||
| Issue Links: |
|
||||
| Assigned Teams: |
Service Arch
|
||||
| Participants: | |||||
| Description |
|
mongo clients can override some parameters (e.g "no cursor timeout") resulting in uncontrollable outcomes. Example : Due to mongo limitations we cannot prevent a client (via a driver) to override the current server setting (including open/close explicit cursors), the alternative we have adopted for now is to alert & detect: 1- Setup an alert for all parameters susceptible of causing perf. issues in DB 2- Isolate offending clients by providing IP address and checking for any driver config update (DBA > through logs and/or mongo shell commands) The option cited above (#1 & #2) is just a temporary measure as we would like to see more flexibility from the DB and back end side. |
| Comments |
| Comment by Lauren Lewis (Inactive) [ 24/Feb/22 ] |
|
We haven’t heard back from you for at least one calendar year, so this issue is being closed. If this is still an issue for you, please provide additional information and we will reopen the ticket. |
| Comment by Bernie Hackett [ 08/Mar/17 ] |
|
Hi. I've moved this ticket to the SERVER project because I believe you are requesting a change to MongoDB rather than the drivers. |