[MDEV-22205] WSREP even if galera not used require almost 2 times more opened files Created: 2020-04-09  Updated: 2020-06-22  Resolved: 2020-06-22

Status: Closed
Project: MariaDB Server
Component/s: N/A
Affects Version/s: 10.1, 10.2, 10.3, 10.4, 10.5
Fix Version/s: N/A

Type: Bug Priority: Blocker
Reporter: Oleksandr Byelkin Assignee: Oleksandr Byelkin
Resolution: Cannot Reproduce Votes: 0
Labels: None


 Description   

Take dSTAR16_MariaDB.sql from MDEV-21447 and try to find with ulimit -n number of file required by server. With WSREP compiled in it is between 2368-2304 without WSREP it is almost 2 times less.

 Comments   
Comment by Oleksandr Byelkin [ 2020-04-09 ]

Do not use mysql-test-run if play with ulimit, because it set its own.

Comment by Jan Lindström (Inactive) [ 2020-04-09 ]

If problem does not repeat WITH_WSREP=OFF it is just matter of grepping WITH_WSREP and finding the offending code by e.g. changing WITH_WSREP with WITH_WSREP_DISABLED until the problem part if found.

Comment by Jan Lindström (Inactive) [ 2020-04-14 ]

e.g. 10.1 startup:

/home/x/maria/git/10.1/sql/mysqld --no-defaults  --basedir=/home/x/maria/git/10.1 --datadir=/home/x/maria/git/10.1/mysql-test/var/install.db --plugin-dir=/home/x/maria/git/10.1/mysql-test/var/plugins --default-storage-engine=myisam --loose-skip-plugin-innodb --loose-skip-plugin-innodb-buffer-page --loose-skip-plugin-innodb-buffer-page-lru --loose-skip-plugin-innodb-buffer-pool-stats --loose-skip-plugin-innodb-changed-pages --loose-skip-plugin-innodb-cmp --loose-skip-plugin-innodb-cmp-per-index --loose-skip-plugin-innodb-cmp-per-index-reset --loose-skip-plugin-innodb-cmp-reset --loose-skip-plugin-innodb-cmpmem --loose-skip-plugin-innodb-cmpmem-reset --loose-skip-plugin-innodb-ft-being-deleted --loose-skip-plugin-innodb-ft-config --loose-skip-plugin-innodb-ft-default-stopword --loose-skip-plugin-innodb-ft-deleted --loose-skip-plugin-innodb-ft-index-cache --loose-skip-plugin-innodb-ft-index-table --loose-skip-plugin-innodb-lock-waits --loose-skip-plugin-innodb-locks --loose-skip-plugin-innodb-metrics --loose-skip-plugin-innodb-mutexes --loose-skip-plugin-innodb-sys-columns --loose-skip-plugin-innodb-sys-datafiles --loose-skip-plugin-innodb-sys-fields --loose-skip-plugin-innodb-sys-foreign --loose-skip-plugin-innodb-sys-foreign-cols --loose-skip-plugin-innodb-sys-indexes --loose-skip-plugin-innodb-sys-semaphore-waits --loose-skip-plugin-innodb-sys-tables --loose-skip-plugin-innodb-sys-tablespaces --loose-skip-plugin-innodb-sys-tablestats --loose-skip-plugin-innodb-tablespaces-encryption --loose-skip-plugin-innodb-tablespaces-scrubbing --loose-skip-plugin-innodb-trx --loose-skip-plugin-partition --loose-skip-plugin-sequence --loose-skip-plugin-xtradb-internal-hash-tables --loose-skip-plugin-xtradb-read-view --loose-skip-plugin-xtradb-rseg --loose-innodb --loose-innodb-log-file-size=5M --disable-sync-frm --tmpdir=/home/x/maria/git/10.1/mysql-test/var/tmp/ --core-file --console --lc-messages-dir=/home/x/maria/git/10.1/sql/share/ --character-sets-dir=/home/x/maria/git/10.1/sql/share/charsets

Comment by Julius Goryavsky [ 2020-05-12 ]

A thorough check was performed both manually and with a modified version of mtr (which does not change "ulimit -n" in safe_processs.cc) - the problem is not confirmed at the moment, the number of open files is the same both when building with wsrep or without. There are very insignificant differences in the operations of writing to files, which are explained by the innodb code in connection with some additions specific to wsrep, but the number of open files remains the same.

Comment by Oleksandr Byelkin [ 2020-05-19 ]

OK, I will recheck

Comment by Oleksandr Byelkin [ 2020-05-19 ]

Yes it looks like it gone

Comment by Jan Lindström (Inactive) [ 2020-06-10 ]

If problem is not repeatable as some comments indicate, this should be closed.

Generated at Thu Feb 08 09:12:59 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.