Aborted_clients metric is growing up even though formal connection close
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MariaDB |
Fix Committed
|
Undecided
|
Vladislav Vaintroub |
Bug Description
I tested MariaDB 5.5.23 with sysbench.
And that time, Aborted_clients metric value is not much grew up.
But, After I applied MariaDB to production database,
Aborted_clients is growing up ever even though normal close of client side.
So, I tested same code with MySQL 5.5.23 community version. But it's okay.
And, MariaDB(with ThreadPool)'s memory usage is really stable under 2GB(Buffer pool is not including)
when I test with sysbench.
But in real service (java application), memory usage is growing up over 6~7GB(without BufferPool).
I'm not sure Aborted_clients metric is related with this memory usage.
Could you check this out ?
Thanks.
after test status-
root@localhost:
+------
| Variable_name | Value |
+------
| Aborted_clients | 100 |
+------
mysql> show global status like 'Aborted_clients';
+------
| Variable_name | Value |
+------
| Aborted_clients | 0 |
+------
test code -------
public class AbortedClientsT
public static void main(String[] args) throws Exception {
Connection[] conns = new Connection[100];
for(int idx=0; idx<100; idx++){
conns[idx] = getConnection();
}
Thread.
for(int idx=0; idx<100; idx++){
conns[
}
}
protected static Connection getConnection() throws Exception {
String driver = "com.mysql.
String url = "jdbc:mysql:
String uid = "sysbench";
String pwd = "sysbench";
Class.
Connection conn = DriverManager.
return conn;
}
}
Related branches
Changed in maria: | |
status: | New → Fix Committed |
Hi,
Could you please provide the cnf file which you are using in production (where you observe the excessive memory consumption?
Thank you.