database/mariadb
1
0
Fork 0
mirror of https://github.com/MariaDB/server.git synced 2025-07-30 16:24:05 +03:00
Code Activity

Bug#14003080:65104: MAX_USER_CONNECTIONS WITH PROCESSLIST EMPTY

Browse Source 
Analysis:
-------------
If server is started with limit of MAX_CONNECTIONS and 
MAX_USER_CONNECTIONS then only MAX_USER_CONNECTIONS of any particular
users can be connected to server and total MAX_CONNECTIONS of client can
be connected to server.

Server maintains a counter for total CONNECTIONS and total CONNECTIONS 
from particular user.

Here, MAX_CONNECTIONS of connections are created to server. Out of this
MAX_CONNECTIONS, connections from particular user (say USER1) are
also created. The connections from USER1 is lesser than 
MAX_USER_CONNECTIONS. After that there was one more connection request from
USER1. Since USER1 can still create connections as he havent reached
MAX_USER_CONNECTIONS, server increments counter of CONNECTIONS per user.
As server already has MAX_CONNECTIONS of connections, next check to total
CONNECTION count fails. In this case control is returned WITHOUT 
decrementing the CONNECTIONS per user. So the counter per user CONNECTIONS goes
on incrementing for each attempt until current connections are closed. 
And because of this counter per CONNECTIONS reached MAX_USER_CONNECTIONS. 
So, next connections form USER1 user always returns with MAX_USER_CONNECTION 
limit error, even when total connection to sever are less than MAX_CONNECTIONS.

Fix:
-------------
This issue is occurred because of not handling counters properly in the
server. Changed the code to handle per user connection counters properly.
This commit is contained in:
Praveenkumar Hulakund
2012-05-28 11:14:43 +05:30
parent b2888adb70
commit b2c3acc987
7 changed files with 200 additions and 73 deletions
Download Patch File Download Diff File Expand all files Collapse all files

86
sql/sql_class.cc
View File

@ -852,7 +852,7 @@ THD::THD()
#if defined(ENABLED_PROFILING)
profiling.set_thd(this);
#endif
user_connect=(USER_CONN *)0;
m_user_connect= NULL;
my_hash_init(&user_vars, system_charset_info, USER_VARS_HASH_SIZE, 0, 0,
(my_hash_get_key) get_var_key,
(my_hash_free_key) free_user_var, 0);
@ -5009,3 +5009,87 @@ bool Discrete_intervals_list::append(Discrete_interval *new_interval)
}
#endif /* !defined(MYSQL_CLIENT) */
void THD::set_user_connect(USER_CONN *uc)
{
DBUG_ENTER("THD::set_user_connect");
m_user_connect= uc;
DBUG_VOID_RETURN;
}
void THD::increment_user_connections_counter()
{
DBUG_ENTER("THD::increment_user_connections_counter");
m_user_connect->connections++;
DBUG_VOID_RETURN;
}
void THD::decrement_user_connections_counter()
{
DBUG_ENTER("THD::decrement_user_connections_counter");
DBUG_ASSERT(m_user_connect->connections > 0);
m_user_connect->connections--;
DBUG_VOID_RETURN;
}
void THD::increment_con_per_hour_counter()
{
DBUG_ENTER("THD::decrement_conn_per_hour_counter");
m_user_connect->conn_per_hour++;
DBUG_VOID_RETURN;
}
void THD::increment_updates_counter()
{
DBUG_ENTER("THD::increment_updates_counter");
m_user_connect->updates++;
DBUG_VOID_RETURN;
}
void THD::increment_questions_counter()
{
DBUG_ENTER("THD::increment_updates_counter");
m_user_connect->questions++;
DBUG_VOID_RETURN;
}
/*
Reset per-hour user resource limits when it has been more than
an hour since they were last checked
SYNOPSIS:
time_out_user_resource_limits()
NOTE:
This assumes that the LOCK_user_conn mutex has been acquired, so it is
safe to test and modify members of the USER_CONN structure.
*/
void THD::time_out_user_resource_limits()
{
mysql_mutex_assert_owner(&LOCK_user_conn);
ulonglong check_time= start_utime;
DBUG_ENTER("time_out_user_resource_limits");
/* If more than a hour since last check, reset resource checking */
if (check_time - m_user_connect->reset_utime >= LL(3600000000))
{
m_user_connect->questions=1;
m_user_connect->updates=0;
m_user_connect->conn_per_hour=0;
m_user_connect->reset_utime= check_time;
}
DBUG_VOID_RETURN;
}