[MDEV-8236] make max_user_connections truly dynamic (as in MySQL) Created: 2015-05-26 Updated: 2015-10-31 |
|
| Status: | Open |
| Project: | MariaDB Server |
| Component/s: | Admin statements |
| Fix Version/s: | None |
| Type: | Task | Priority: | Minor |
| Reporter: | Martin Amps | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Description |
|
The attached statement runs fine on MySQL, but not on MariaDB per this commit in 2011: https://github.com/MariaDB/server/commit/7800d93bc3caca0143334941f626dc6aa3ff2b26
The process doesn't have such an option as shown by ps:
|
| Comments |
| Comment by Sergei Golubchik [ 2015-05-28 ] |
|
This is done to fix the following bug: in MySQL if you set max_user_connections run-time, then existing connections won't be counted. You can set it to 10, but a user can already have a thousand of connections and he'll be able to open ten more. A possible fix would be always to count user connections, but it would introduce an overhead for those many users, who don't use connection limits. MariaDB has implemented a different fix — don't count connections if started with max_user_connections=0, but don't allow max_user_connections to be set to non-zero value, because a correct connection counting in that case cannot be guaranteed. There are other ways to fix this bug, we can consider them. |
| Comment by Kolbe Kegel (Inactive) [ 2015-05-29 ] |
|
I would like to see MariaDB use some other solution, so that max_user_connections is truly a dynamic variable. |
| Comment by Sergei Golubchik [ 2015-05-29 ] |
|
kolbe, yes, exactly. That's why it's a "Task", not a "Bug", and that's why it's not closed as "Won't Fix". |