Are these settings good enough for Mariadb?

Richard G

Richard G

Verified User
Joined
Jul 6, 2008
Messages
12,775
Location
Maastricht
I'm not looking to perfectly tune the servers, but they should run good.

I just seen this in another thread:
Zhenyapan said:
table_definition_cache=25000
Click to expand...
How do you calculate that? Is this needed? I don't know the defaults.

I got this on one server:
Code: 
MariaDB [(none)]> show global status  like 'open%';
+--------------------------+--------+
| Variable_name            | Value  |
+--------------------------+--------+
| Open_files               | 409    |
| Open_streams             | 0      |
| Open_table_definitions   | 2732   |
| Open_tables              | 3999   |
| Opened_files             | 583242 |
| Opened_plugin_libraries  | 0      |
| Opened_table_definitions | 4966   |
| Opened_tables            | 7376   |
| Opened_views             | 16     |
+--------------------------+--------+
Dont have any cache set yet, but got this in my.cnf

Code: 
[mysqld]
local-infile = 0
bind-address = 127.0.0.1
skip-name-resolve=1

max_connections = 300

sql_mode=
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
tmp_table_size=512M
max_heap_table_size=512M
innodb_buffer_pool_size=6144M
innodb_buffer_pool_instances=4
innodb_log_file_size=256M
join_buffer_size=2M

We got a dedi i7-7700 with 64 GB of Ram. Would this be a good enough setting?

Other server is the same, but has this output to the same command at this moment:
Code: 
MariaDB [(none)]> show global status  like 'open%';
+--------------------------+--------+
| Variable_name            | Value  |
+--------------------------+--------+
| Open_files               | 34     |
| Open_streams             | 0      |
| Open_table_definitions   | 1822   |
| Open_tables              | 2000   |
| Opened_files             | 450461 |
| Opened_plugin_libraries  | 0      |
| Opened_table_definitions | 21831  |
| Opened_tables            | 12375  |
| Opened_views             | 14     |
+--------------------------+--------+
9 rows in set (0.000 sec)
 
"table_definition_cache" should set along with "open_files_limit" .

open_files_limit, I alway set to 50000.
because I have too many project, can't remember too much thing.
I will make some value into default for mine ( without needed to calculate or re-edit).

And always increase limit "soft, hard" nofile for globals server. ( Incase something needed).
 
@johannes I've seen that link too, but it said:
Table cache hit rate = table_open_cache*100/Opened_tables
Click to expand...
Which is why I asked over here, because I don't know where to get my current table_open_cache value.
Seems default to 2000. So 2000*100=200.000 / 7376 = 27,11. On the second server it would be 200.000 / 12375 = 16,16. So these are my cache hit rates.
Table_open_cache = total_tables*Threads_connected it says. Where can I find these values? I'm not really into database stuff. :)

jamgames2 said:
open_files_limit, I alway set to 50000.
because I have too many project, can't remember too much thing.
Click to expand...
Why so high? Is that because ou have so many projects? Since I have a lot of opened_files (1st server 58k). Does this mean I also need to set this to 50000?

Your link I gave the command: cat /proc/sys/fs/file-max and the result was on all servers 6457106 which seems default to me then ,because I didn't change anything.
jamgames2 said:
"table_definition_cache" should set along with "open_files_limit" .
Click to expand...
I don't have either setting in the my.cnf file so I'm using the defaults then.

I have run mysqltuner a while ago, and it seemd to me the settins I got were good. But now I've seen the skip-name-resolve which I hadn't yet and I wonder if the cache setting would improve performance. But then I need to know how to calculate it.

So if I set the open_files_limit to 50000 do I need to set the table_definition_cache also to 50000 or to anoter value?
 
"table_definition_cache" should lower than "open_files_limit"

"open_files_limit" be like limit "soft, hard" nofile.

if "table_definition_cache" greater than 65535, 50000 should be fine.
because too much openfile, too much workloads on disk IO.

total_tables , Threads_connected also can find from SQL Query. like
Code: 
SHOW STATUS WHERE `variable_name` = 'Threads_connected';

Something hard to remember, so I fix it to 50000.

but it long ago I tuning my server. I found similar that I used in the past.
 
Thank you. I will have a look at this. The table_definition_cache defaults to 2000 in MariaDB i've read. At this moment my database is working quick so I have a search for the values with the command you gave.
And then have a look at the link you posted to see if I should indeed need to change some things or leave it as is.
 
I took table_definition_cache from his mysqltuner recommendations.
"table_definition_cache(1400) > 22904 or -1 (autosizing if supported)"
but it's ok to keep it at least 1/3 of total mysql tables.
 
On the first server mysqltuner 1.7.21 says this.
Code: 
General recommendations:
    /var/log/mysql/mysqld.log is > 32Mb, you should analyze why or implement a rotation log strategy such as logrotate!
    Control warning line(s) into /var/log/mysql/mysqld.log file
    Control error line(s) into /var/log/mysql/mysqld.log file
    MySQL was started within the last 24 hours - recommendations may be inaccurate
    Reduce your overall MySQL memory footprint for system stability
    Dedicate this server to your database for highest performance.
    Reduce or eliminate unclosed connections and network issues
    We will suggest raising the 'join_buffer_size' until JOINs not using indexes are found.
             See https://dev.mysql.com/doc/internals/en/join-buffer-size.html
             (specially the conclusions at the bottom of the page).
    Temporary table size is already large - reduce result set size
    Reduce your SELECT DISTINCT queries without LIMIT clauses
    Performance schema should be activated for better diagnostics
    Consider installing Sys schema from https://github.com/mysql/mysql-sys for MySQL
    Consider installing Sys schema from https://github.com/FromDual/mariadb-sys for MariaDB
    Before changing innodb_log_file_size and/or innodb_log_files_in_group read this: https://bit.ly/2TcGgtU
Variables to adjust:
  *** MySQL's maximum memory usage is dangerously high *** <---?? I don't understand why this is.
  *** Add RAM before increasing MySQL buffer variables ***
    join_buffer_size (> 2.0M, or always use indexes with JOINs)
    table_definition_cache(400) > 4646 or -1 (autosizing if supported)
    performance_schema = ON enable PFS
    innodb_log_file_size should be (=768M) if possible, so InnoDB total log files size equals to 25% of buffer pool size.
    innodb_buffer_pool_instances(=6)

Second server mysqltuner 1.7.3 says this
Code: 
General recommendations:
    Control warning line(s) into /var/log/mysql/mysqld.log file
    Control error line(s) into /var/log/mysql/mysqld.log file
    Remove Anonymous User accounts - there are 2 anonymous accounts.
    Set up a Password for user with the following SQL statement ( SET PASSWORD FOR 'user'@'SpecificDNSorIp' = PASSWORD('secure_password'); )
    Set up a Secure Password for user@host ( SET PASSWORD FOR 'user'@'SpecificDNSorIp' = PASSWORD('secure_password'); )
    MySQL started within last 24 hours - recommendations may be inaccurate
    Adjust your join queries to always utilize indexes
    Performance should be activated for better diagnostics
    Consider installing Sys schema from https://github.com/mysql/mysql-sys
Variables to adjust:
    query_cache_size (=0)
    query_cache_type (=0)
    query_cache_limit (> 1M, or use smaller result sets)
    join_buffer_size (> 256.0K, or always use indexes with joins)
    performance_schema = ON enable PFS
    innodb_buffer_pool_size (>= 1G) if possible.
    innodb_log_file_size should be (=16M) if possible, so InnoDB total log files size equals to 25% of buffer pool size.
 
just download fresh mysqltuner:
wget mysqltuner.pl
if it downloaded as index.html
just
mv index.html mysqltuner.pl
chmod +x mysqltuner.pl
run and check.
 
*** MySQL's maximum memory usage is dangerously high *** <---?? I don't understand why this is. - because max_allowed_packet *max_connections = a lot of gigabytes.
*** Add RAM before increasing MySQL buffer variables ***
join_buffer_size (> 2.0M, or always use indexes with JOINs)
table_definition_cache(400) > 4646 or -1 (autosizing if supported) - so you can set 5000 for future table count increase
performance_schema = ON enable PFS - enable only temporary to collect and analyze this log (if you know how to)
innodb_log_file_size should be (=768M) if possible, so InnoDB total log files size equals to 25% of buffer pool size. - if already 512 - you can leave 512.
innodb_buffer_pool_instances(=6) - one instance per 1gb of buffer pool (in fresh maria 10.5,10.6 etc - it's auto)
--------------
Remove Anonymous User accounts - there are 2 anonymous accounts.
Set up a Password for user with the following SQL statement ( SET PASSWORD FOR 'user'@'SpecificDNSorIp' = PASSWORD('secure_password'); )
Set up a Secure Password for user@host ( SET PASSWORD FOR 'user'@'SpecificDNSorIp' = PASSWORD('secure_password'); )
MySQL started within last 24 hours - recommendations may be inaccurate
Adjust your join queries to always utilize indexes
Performance should be activated for better diagnostics
Consider installing Sys schema from https://github.com/mysql/mysql-sys
Variables to adjust:
query_cache_size (=0) - depens on MyIsam databases size/load
query_cache_type (=0)
query_cache_limit (> 1M, or use smaller result sets)
join_buffer_size (> 256.0K, or always use indexes with joins)
performance_schema = ON enable PFS
innodb_buffer_pool_size (>= 1G) if possible. - give it 1G
innodb_log_file_size should be (=16M) if possible, so InnoDB total log files size equals to 25% of buffer pool size. - increase to 16m too (it's 5m by default on some versions)
 
I think mysqltuner does not use all values correctly. I downloaded the newest version (2.04) and ran it, but has almost the same output.

Zhenyapan said:
because max_allowed_packet *max_connections = a lot of gigabytes.
Click to expand...
Oh that's bad indeed. My max_connections is 300 as you can see from the my.cnf in post #1. But 300 connections isn't that high is it? My max_allowed_packet was set to 256M on two servers, looks like the default in /etc/my.cnf.d/server.cnf but in the latest server it's only 64M.
So I will decrease that to 64M, that is a good value?

I change some settings now which you advised and test later again if it's still correct

But I have added this:
skip-name-resolve=1

But this causes databases to fail, because they are not allowed to connect to 127.0.0.1. So when I change this in the config of the websites using this to "localhost" then all is fine.

Is this setting really beneficial? Or can I just as well leave it out so people can also use 127.0.0.1 to connect?
 
Also, how can I remove those?
Remove Anonymous User accounts - there are 2 anonymous accounts.
Click to expand...
I tried getting a list with the SELECT User FROM mysql.user; command but I don't see any anonymous.
 
it's maximum theoretical, in case when all this 300 connections will make simultaneously requests that will need 256mb each.
so don't worry about this :)
---
skip-name-resolve=1 - it's more for end users, to make them put as host: localhost or 127.0.0.1, because some may put there their domain names - and resolving this domain names takes a lot of time.
----
to remove mysql user from console - sometimes you must after login run:
USE mysql;
or
DELETE FROM mysql.user WHERE User='';
and other variants, syntax depends on exact mysql version.
easier way - login to PhpMyadmin with da_admin credentials and via GUI find and remove user, there is less chance to drop something important.
of course - make backup before any critical changes
 
example one of client servers: dual xeon e5-2680v4 (28c/56t) 256RAM 2x1tb NVME raid1 mysql
[root@server src]# ./mysqltuner.pl
>> MySQLTuner 1.8.5 - Major Hayden <[email protected]>
>> Bug reports, feature requests, and downloads at http://mysqltuner.pl/
>> Run with '--help' for additional options and output filtering

[--] Skipped version check for MySQLTuner script
[OK] Currently running supported MySQL version 10.5.15-MariaDB-cll-lve
[OK] Operating on 64-bit architecture

-------- Log file Recommendations ------------------------------------------------------------------
[OK] Log file /var/log/mysql/mysql_error.log exists
[--] Log file: /var/log/mysql/mysql_error.log(1G)
[OK] Log file /var/log/mysql/mysql_error.log is not empty
[!!] Log file /var/log/mysql/mysql_error.log is bigger than 32 Mb
[OK] Log file /var/log/mysql/mysql_error.log is readable.
[!!] /var/log/mysql/mysql_error.log contains 6556 warning(s).
[!!] /var/log/mysql/mysql_error.log contains 32 error(s).
[--] 0 start(s) detected in /var/log/mysql/mysql_error.log
[--] 0 shutdown(s) detected in /var/log/mysql/mysql_error.log

-------- Storage Engine Statistics -----------------------------------------------------------------
[--] Status: +Aria +CSV +InnoDB +MEMORY +MRG_MyISAM +MyISAM +PERFORMANCE_SCHEMA +SEQUENCE
[--] Data in MyISAM tables: 28.9G (Tables: 32572) - there is sense to use query_cache - also there is total 63k tables, so cached can be all or at least 1/4
[--] Data in InnoDB tables: 42.6G (Tables: 30324) - there it takes recommended innodb buffer pool size = 42G
[--] Data in MEMORY tables: 1.1M (Tables: 182)
[!!] Total fragmented tables: 5

-------- Analysis Performance Metrics --------------------------------------------------------------
[--] innodb_stats_on_metadata: OFF
[OK] No stat updates during querying INFORMATION_SCHEMA.

-------- Security Recommendations ------------------------------------------------------------------
[!!] User 'nagios'@% does not specify hostname restrictions.
[!!] User 'webme'@% does not specify hostname restrictions.

-------- CVE Security Recommendations --------------------------------------------------------------
[--] Skipped due to --cvefile option undefined

-------- Performance Metrics -----------------------------------------------------------------------
[--] Up for: 40d 8h 23m 26s (2B q [630.699 qps], 31M conn, TX: 45925G, RX: 601G)
[--] Reads / Writes: 93% / 7%
[--] Binary logging is disabled
[--] Physical Memory : 251.6G
[--] Max MySQL memory : 100.6G
[--] Other process memory: 0B
[--] Total buffers: 51.2G global + 194.9M per thread (260 max threads) -here your ram warning 1
[--] P_S Max memory usage: 0B
[--] Galera GCache Max memory usage: 0B
[OK] Maximum reached memory usage: 78.8G (31.30% of installed RAM) - here current MAX consumption
[OK] Maximum possible memory usage: 100.6G (40.00% of installed RAM) - here your ram warning 2
[OK] Overall possible memory usage with other process is compatible with memory available
[OK] Slow queries: 0% (356K/2B)
[OK] Highest usage of available connections: 55% (145/260)
[OK] Aborted connections: 2.48% (770002/31001738) - due to inactivity timeout or killed by mysql_governor (cloudlinux)
[!!] name resolution is active : a reverse name resolution is made for each new connection and can reduce performance
[OK] Query cache is disabled by default due to mutex contention on multiprocessor machines.
[OK] Sorts requiring temporary tables: 0% (651K temp sorts / 539M sorts)
[!!] Joins performed without indexes: 6540756
[!!] Temporary tables created on disk: 67% (171M on disk / 255M total) - it this case ignored due to separate inRAM tmp dir
[OK] Thread cache hit rate: 99% (145 created / 31M connections)
[OK] Table cache hit rate: 99% (3B hits / 3B requests)
[!!] table_definition_cache(30000) is lower than number of tables(63344) - but at least it's bigger than default 1400
[OK] Open file limit used: 8% (27K/320K) - better to keep limit high enough for future
[OK] Table locks acquired immediately: 99% (2B immediate / 2B locks)

-------- Performance schema ------------------------------------------------------------------------
[--] Performance schema is disabled.
[--] Memory used by P_S: 0B
[--] Sys schema isn't installed.

-------- ThreadPool Metrics ------------------------------------------------------------------------
[--] ThreadPool stat is enabled.
[--] Thread Pool Size: 56 thread(s).
[--] Using default value is good enough for your version (10.5.15-MariaDB-cll-lve)

-------- MyISAM Metrics ----------------------------------------------------------------------------
[!!] Key buffer used: 25.1% (1B used / 6B cache)
[OK] Key buffer size / total MyISAM indexes: 6.0G/6.7G - recommeded to keep equal, but in previous string you can see that it uses only 25% during last 40 days uptime, that's why check and tune as really needed, start from 1/2
[OK] Read Key buffer hit rate: 100.0% (191B cached / 63M reads)
[!!] Write Key buffer hit rate: 62.5% (62M cached / 38M writes)

-------- InnoDB Metrics ----------------------------------------------------------------------------
[--] InnoDB is enabled.
[--] InnoDB Thread Concurrency: 0
[OK] InnoDB File per table is activated
[!!] InnoDB buffer pool / data size: 40.0G/42.6G
[!!] Ratio InnoDB log file size / InnoDB Buffer pool size (5 %): 2.0G * 1/40.0G should be equal to 25% - 2G makes restart about 1 minute, recommended 10G will take up to 5 minutes + in case of crash - repair will take up to 1 hour :( thats why only 2G
[--] Number of InnoDB Buffer Pool Chunk : 320 for 1 Buffer Pool Instance(s)
[OK] Innodb_buffer_pool_size aligned with Innodb_buffer_pool_chunk_size & Innodb_buffer_pool_instances
[OK] InnoDB Read buffer efficiency: 100.00% (502307653762 hits/ 502309962675 total)
[!!] InnoDB Write Log efficiency: 962.64% (77896164 hits/ 8091931 total)
[OK] InnoDB log waits: 0.00% (0 waits / 85988095 writes)

-------- Aria Metrics ------------------------------------------------------------------------------
[--] Aria Storage Engine is enabled.
[OK] Aria pagecache size / total Aria indexes: 128.0M/616.0K
[OK] Aria pagecache hit rate: 98.2% (9B cached / 163M reads)

-------- Recommendations ---------------------------------------------------------------------------
General recommendations:
/var/log/mysql/mysql_error.log is > 32Mb, you should analyze why or implement a rotation log strategy such as logrotate!
Check warning line(s) in /var/log/mysql/mysql_error.log file
Check error line(s) in /var/log/mysql/mysql_error.log file
Run OPTIMIZE TABLE to defragment tables for better performance
OPTIMIZE TABLE `123world_viktorqp_bee`.`modx_session`; -- can free 424.25708770752 MB
OPTIMIZE TABLE `123rkc_rnr`.`cache_page`; -- can free 1163.20782470703 MB
OPTIMIZE TABLE `123veln_db`.`cache_data`; -- can free 162 MB
OPTIMIZE TABLE `123veln_db`.`cache_render`; -- can free 100 MB
OPTIMIZE TABLE `123arant_w`.`wp_postmeta`; -- can free 58 MB
Total freed space after theses OPTIMIZE TABLE : 1907.46491241455 Mb

Variables to adjust:
join_buffer_size (> 256.0K, or always use indexes with JOINs)
table_definition_cache(30000) > 63344 or -1 (autosizing if supported)
performance_schema = ON enable PFS
innodb_buffer_pool_size (>= 42.6G) if possible.
innodb_log_file_size should be (=10G) if possible, so InnoDB total log files size equals to 25% of buffer pool size.
and so on...
optimal to tune mysql that has at least 48h uptime, there is no sense to tune all parameters up to 100% - you can't, if it is not a one fixed project DB, it's shared hosting wit different DBs that can be changed every day. So good values near 75+%
 
You need to be careful with some of the settings that affect the per thread variable. As @Zhenyapan points out that is why you are getting the max memory warning. As goes the normal warning about being careful about what you read and do, here are a couple of sites I found at least informative.

github.com

What goes in to defining the "per thread" memory calculation · Issue #481 · major/MySQLTuner-perl

Hello! Sorry, I'm relatively new to MySQL tuning and I've been looking in a couple of places to work out how exactly to optimize my db config. Are you able to confirm what goes in to the &q...
github.com github.com

gist.github.com

my.cnf

my.cnf. GitHub Gist: instantly share code, notes, and snippets.
gist.github.com gist.github.com

This does seem high
max_allowed_packet was set to 256M

MySQL :: MySQL 8.0 Reference Manual :: 5.1.8 Server System Variables

dev.mysql.com dev.mysql.com

MySQL :: MySQL 8.0 Reference Manual :: 11.3.4 The BLOB and TEXT Types

dev.mysql.com dev.mysql.com

Generally, the defaults now are pretty good in mariadb and mysql. In terms of max_allowed_packet, you will see some recommendations to set it to 16MB, the default is 64MB, I have mine set to 48MB.
 
Zhenyapan said:
easier way - login to PhpMyadmin with da_admin credentials and via GUI find and remove user, there is less chance to drop something important.
Click to expand...
I did that, but couldn't find the anonymous user. I used another command via mysql commandline which showed users and allowed logins.
The 2 anonymous were one anonymous localhost and one on the hostname. So I delete both, worked good.

As for the memory, my newest server is also 64M so I set that back and now that warning is gone and everything works still flawlessly. However I now know that I can raise that value if needed.

@BillyS Thank you too. However, I can't use those references because I'm not running Mysql, I'm running MariaDB. So I used this information yesterday to see and find out some things.
mariadb.com

Server System Variables

List of system variables.
mariadb.com mariadb.com


Zhenyapan said:
[!!] /var/log/mysql/mysql_error.log contains 6556 warning(s).
[!!] /var/log/mysql/mysql_error.log contains 32 error(s).
Click to expand...
Oh mine is now:
[!!] /var/log/mysql/mysqld.log contains 18139 warning(s).
[!!] /var/log/mysql/mysqld.log contains 3121 error(s).

Output of the mysqltuner now:
Code: 
Variables to adjust:
    skip-name-resolve=1
    join_buffer_size (> 256.0K, or always use indexes with JOINs)
    performance_schema=ON
    key_buffer_size (~ 24M)
Before that join buffer sizes was at 2 MB, but even on 20 MB it keeps saying to put that more than the given value, so I removed the setting in my.cnf and now it's default again.

The other server has the same output, but less errors:
Code: 
[!!] /var/log/mysql/mysqld.log contains 1279 warning(s).
[!!] /var/log/mysql/mysqld.log contains 401 error(s).

But probably the one with the lots of errors, looks at errors which were in the log before.

On restart of mariadb and also since then, I don't see any errors in te log. Unless somebody sees something wrong?
Code: 
2022-07-07  1:19:18 0 [Note] /usr/sbin/mysqld (initiated by: unknown): Normal shutdown
2022-07-07  1:19:18 0 [Note] Event Scheduler: Purging the queue. 0 events
2022-07-07  1:19:18 0 [Note] InnoDB: FTS optimize thread exiting.
2022-07-07  1:19:18 0 [Note] InnoDB: Starting shutdown...
2022-07-07  1:19:18 0 [Note] InnoDB: Dumping buffer pool(s) to /var/lib/mysql/ib_buffer_pool
2022-07-07  1:19:18 0 [Note] InnoDB: Instance 0, restricted to 24081 pages due to innodb_buf_pool_dump_pct=25
2022-07-07  1:19:18 0 [Note] InnoDB: Instance 1, restricted to 24081 pages due to innodb_buf_pool_dump_pct=25
2022-07-07  1:19:18 0 [Note] InnoDB: Instance 2, restricted to 24081 pages due to innodb_buf_pool_dump_pct=25
2022-07-07  1:19:18 0 [Note] InnoDB: Instance 3, restricted to 24081 pages due to innodb_buf_pool_dump_pct=25
2022-07-07  1:19:18 0 [Note] InnoDB: Buffer pool(s) dump completed at 220707  1:19:18
2022-07-07  1:19:20 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2022-07-07  1:19:20 0 [Note] InnoDB: Shutdown completed; log sequence number 680533651079; transaction id 371684664
2022-07-07  1:19:20 0 [Note] /usr/sbin/mysqld: Shutdown complete

2022-07-07  1:19:20 0 [Note] InnoDB: Using Linux native AIO
2022-07-07  1:19:20 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2022-07-07  1:19:20 0 [Note] InnoDB: Uses event mutexes
2022-07-07  1:19:20 0 [Note] InnoDB: Compressed tables use zlib 1.2.7
2022-07-07  1:19:20 0 [Note] InnoDB: Number of pools: 1
2022-07-07  1:19:20 0 [Note] InnoDB: Using SSE2 crc32 instructions
2022-07-07  1:19:20 0 [Note] InnoDB: Initializing buffer pool, total size = 6G, instances = 4, chunk size = 128M
2022-07-07  1:19:20 0 [Note] InnoDB: Completed initialization of buffer pool
2022-07-07  1:19:20 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2022-07-07  1:19:20 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2022-07-07  1:19:20 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2022-07-07  1:19:20 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2022-07-07  1:19:20 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.
2022-07-07  1:19:20 0 [Note] InnoDB: Waiting for purge to start
2022-07-07  1:19:20 0 [Note] InnoDB: 10.4.25 started; log sequence number 680533651079; transaction id 371684638
2022-07-07  1:19:20 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
2022-07-07  1:19:20 0 [Note] Plugin 'FEEDBACK' is disabled.
2022-07-07  1:19:20 0 [Note] Server socket created on IP: '127.0.0.1'.
2022-07-07  1:19:20 0 [Note] Reading of all Master_info entries succeeded
2022-07-07  1:19:20 0 [Note] Added new Master_info '' to hash table
2022-07-07  1:19:20 0 [Note] /usr/sbin/mysqld: ready for connections.
Version: '10.4.25-MariaDB-log'  socket: '/var/lib/mysql/mysql.sock'  port: 3306  MariaDB Server
2022-07-07  1:19:23 0 [Note] InnoDB: Buffer pool(s) load completed at 220707  1:19:23

I only have to check what this means I guess.
If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
Click to expand...
 
maybe your log not rotated, my too :)
so this errors can be few months ago or more - just check sometimes logs.
---
join_buffer_size - i keep default too, it makes impact for few databases that needed it, for all other 99% clients defaults enough.
 
Thanks, then I don't need to worry about that setting. That's good.

I think I'm going to add the log to logrotate, is 145M so not that big, but there are errors from 2019 in there too. :)
 
You must log in or register to reply here.
Back
Top