Question max_open_files request:32190

[Dukemaster]

After MariaDB Upgrade 10.3 to 10.5 on Ubuntu 18.04.5 server I watched status and get the [Warning] Could not increase number of max_open_files to more than 8192 (request: 32190)
Is it okay and good to increase number of max_open_files to such high numbers?

Please, what do you suggest?

Greets

Here is the complete output:

root@server:~# systemctl status mariadb
● (<- green) mariadb.service - MariaDB 10.5.5 database server
   Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)
  Drop-In: /etc/systemd/system/mariadb.service.d
           └─migrated-from-my.cnf-settings.conf, override.conf
   Active: active (running) since Thu 2020-09-24 13:12:55 CEST; 1 day 8h ago
     Docs: man:mariadbd(8)
           https://mariadb.com/kb/en/library/systemd/
Main PID: 2860 (mariadbd)
   Status: "Taking your SQL requests now..."
    Tasks: 32 (limit: 4915)
   CGroup: /system.slice/mariadb.service
           └─2860 /usr/sbin/mariadbd

Sep 24 13:12:24 server.example.com systemd[1]: Starting MariaDB 10.5.5 database server...
Sep 24 13:12:32 server.example.com mariadbd[2860]: 2020-09-24 13:12:32 0 [Note] /usr/sbin/mariadbd (mysqld 10.5.5-MariaDB-1:10.5.5+maria~bionic) starting as process 2860 ..
Sep 24 13:12:32 server.example.com mariadbd[2860]: 2020-09-24 13:12:32 0 [Warning] Could not increase number of max_open_files to more than 8192 (request: 32190)
Sep 24 13:12:55 server.example.com systemd[1]: Started MariaDB 10.5.5 database server.
Sep 24 13:12:57 server.example.com /etc/mysql/debian-start[6547]: /usr/bin/mysql_upgrade: the '--basedir' option is always ignored
Sep 24 13:12:57 server.example.com /etc/mysql/debian-start[6547]: Looking for 'mysql' as: /usr/bin/mysql
Sep 24 13:12:57 server.example.com /etc/mysql/debian-start[6547]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck
Sep 24 13:12:57 server.example.com /etc/mysql/debian-start[6547]: This installation of MariaDB is already upgraded to 10.5.5-MariaDB, use --force if you still need to run m

root@server:~#

 

[Bitpalast]

Here is a good article that addresses the warning message:

Could not increase number of max_open_files to more than... (Solution)

A quick solution to the warning "Could not increase number of max_open_files to more than" when starting MySQL or MariaDB. For some background, read How

haydenjames.io

For today's normal usage, a number like 32190 is not only appropriate, it might even be too low. On our systems, we normally have a six figure number for open files. It depends on how many connections you have to the server, how many files are open at the same time etc. The more users are on the system, the more databases, the more tables, the higher the limit needs to be.