image-2021-11-20-09-06-15-096.png
[MXS-3887] Hide the Timeout option from SQL editor for Basic Users(--type=basic) Created: 2021-11-20 Updated: 2023-10-04 Resolved: 2023-10-04 |
|
| Status: | Closed |
| Project: | MariaDB MaxScale |
| Component/s: | N/A |
| Affects Version/s: | None |
| Fix Version/s: | N/A |
| Type: | New Feature | Priority: | Major |
| Reporter: | Naresh Chandra | Assignee: | Todd Stoffel (Inactive) |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Attachments: |
image-2021-11-20-09-06-15-096.png
|
| Description |
|
Can you please hide the Timeout option from SQL editor for only basic users. So please add Timeout option in the maxscale.cnf file, so that Admin can only increase the Timeout value in the maxscale.cnf filw whenever its required. |
| Comments |
| Comment by markus makela [ 2021-11-20 ] |
|
Hiding the timeout won't prevent users from doing stupid things that lock up the whole database. If a connection times out while doing a massive query, the query will continue being processed (might depend on exactly what is being done). A more effective way of controlling this might be to use User-level max_statement_time. |
| Comment by Naresh Chandra [ 2021-11-20 ] |
|
Yes, Markus I agree with you. If we have more than 100 users, its typical to update all the users and need to identify.. So that's why we are expecting if can give at least in the maxscale.cnf level parameter that would be good. sql_editor_time_out=3000s like this we are expecting. so that we can control the users from the maxscale.cnf file itself. |
| Comment by Johan Wikman [ 2023-10-04 ] |
|
Add ticket to the server. E.g. per user configuration limits. |
