[MDEV-3848] MariaDB Galera Cluster Memory Usage growing Created: 2012-11-10 Updated: 2018-04-04 Resolved: 2018-04-04 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Galera |
| Affects Version/s: | 5.5.25-galera |
| Fix Version/s: | 5.5.60 |
| Type: | Bug | Priority: | Minor |
| Reporter: | Kari Lehtinen | Assignee: | Sachin Setiya (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Environment: |
Centos 6.1 64-bit |
||
| Description |
|
I'm evaluating MariaDB cluster and I see massive grow in memory usage compared to Standalone MariaDB installation. Cluster tests are done in 3 Node envinronment. With Centos 6.1 and 1GB RAM. Basically replication is working fine between these nodes, but memory usage grows all the time without releasing it which makes it kinda unusable. 3 Node cluster Setup running following packages Node 1 my.cnf: [mysqld] wsrep_provider=/usr/lib64/galera/libgalera_smm.so innodb_locks_unsafe_for_binlog=1 Node 2/3 has identical my.cnf except wsrep_node_name and wsrep_cluster_address parameters. create database ptest; node1 PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND Nodes 2 and 3 has almost same memory usage so eventually all nodes will run out memory if inserts are continued. Executing same test with standalone MariaDB with same InnoDB settings keeps memory as low as 116M. STANDALONE MARIADB MariaDB-common-5.5.28-1.x86_64 PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND What could be causing this ? MariaDB cluster guide states are memory usage should increase only slightly compared to standalone installation. |
| Comments |
| Comment by Elena Stepanova [ 2012-11-10 ] |
|
I won't double-check it since it's consistent with my earlier observations, see |
| Comment by Seppo Jaakola [ 2012-11-28 ] |
|
This test runs larger and larger transactions and in the end the size of the transaction is ~1M rows. Galera does not currently support arbitarily large transactions. There are configuration variables 'wsrep_max_ws_rows' and 'wsrep_max_ws_size' to abort huge transaction before OOM would happen. Huge transaction support is in design phase and will be part of some future release. |
| Comment by Sachin Setiya (Inactive) [ 2018-04-04 ] |
|
This will be sorted in galera 4 release |