Null Mysql Daemon Innodb Process

[Mayc]

mysql and I suspect it is related to these processes. I put a ticket in support and they tell me it's not a cpanel problem. Does anyone have any idea what it might be or how to eliminate them?
normally on other servers looks like this


but on this machine it looks like this and they have the same configuration in everything.


Thanks
Note to moderator: please remove my old post about this.thanks

 

[24x7server]

Hi,

What you see is the InnoDB settings on the server, which is a custom setting not a regular MySQL setting provided by cPanel by default.. Can you share the output of the below command:
# cat my.cnf

 

[Mayc]

Hi,

What you see is the InnoDB settings on the server, which is a custom setting not a regular MySQL setting provided by cPanel by default.. Can you share the output of the below command:
# cat my.cnf

thanks

[client]
port                            = 3306
socket                          = /var/lib/mysql/mysql.sock

[mysqld-safe]
socket                          = /var/lib/mysql/mysql.sock
nice                            = 0

[mysqld]
# Basic
basedir                         = /usr
bind-address                    = 127.0.0.1 # Comment out if you want remote servers to connect to this server's MySQL instance
datadir                         = /var/lib/mysql
lc-messages-dir                 = /usr/share/mysql
max-allowed-packet              = 128M
max-connect-errors              = 1000000
pid-file                        = /var/lib/mysql/mysql.pid
port                            = 3306
skip-external-locking
skip-name-resolve
socket                          = /var/lib/mysql/mysql.sock
tmpdir                          = /tmp
user                            = mysql

# InnoDB Settings
default-storage-engine          = InnoDB
innodb-buffer-pool-instances    = 8     # Use 1 instance per 1GB of InnoDB pool size
innodb-buffer-pool-size         = 100G    # Use up to 70-80% of RAM & optionally check if /proc/sys/vm/swappiness is set to 0
innodb-file-per-table           = 1
innodb-flush-log-at-trx-commit  = 0
innodb-flush-method             = O_DIRECT
innodb-log-buffer-size          = 16M
innodb-log-file-size            = 128M
#innodb-thread-concurrency      = 6     # Optional: Set to the number of CPUs on your system (minus 1 or 2) to better contain CPU usage
                                        # E.g. if your system has 8 CPUs, try 6 or 7 and check the overall load from MySQL.

# MyISAM Query Cache Settings
query-cache-limit               = 4M    # UPD
query-cache-size                = 48M   # UPD
query-cache-type                = 1

key-buffer-size                 = 48M   # UPD

low-priority-updates            = 1
concurrent-insert               = 2

# Common
max-connections                 = 100   # UPD
back-log                        = 512

wait-timeout                    = 90
interactive-timeout             = 90

join-buffer-size                = 2M    # UPD
read-buffer-size                = 2M    # UPD
read-rnd-buffer-size            = 4M    # UPD
sort-buffer-size                = 4M    # UPD

thread-cache-size               = 100   # UPD (most of the times you probably won't need to change this)
thread-stack                    = 192K

max-heap-table-size             = 128M
tmp-table-size                  = 128M

table-definition-cache          = 8000  # UPD
table-open-cache                = 8000  # UPD
open-files-limit                = 24000 # UPD

ft-min-word-len                 = 3     # Minimum length of words to be indexed for search results

expire-logs-days                = 7
log-error                       = /var/lib/mysql/mysql_error.log
log-queries-not-using-indexes   = 1
long-query-time                 = 8
max-binlog-size                 = 100M
slow-query-log                  = 1
slow-query-log-file             = /var/lib/mysql/mysql_slow.log

[mysqldump]
quick
quote-names
max-allowed-packet              = 16M

[mysql]

[isamchk]
key-buffer-size                 = 16M

 

[cPWilliamL]

What are the MySQL versions on the two different servers? Are you seeing any issues from these processes? I don't believe there should be any concern or issue with these processes. I believe this is a new threaded purge feature in MySQL(see slide 13):
https://www.mysql.com/news-and-events/events/VDD-MySQL-July13/New_InnoDB_Feature_MySQL_5.6_Jimmy.pdf
MySQL :: MySQL 5.7 Reference Manual :: 14.6.11 Configuring InnoDB Purge Scheduling

 

[Mayc]

What are the MySQL versions on the two different servers? Are you seeing any issues from these processes? I don't believe there should be any concern or issue with these processes. I believe this is a new threaded purge feature in MySQL(see slide 13):
https://www.mysql.com/news-and-events/events/VDD-MySQL-July13/New_InnoDB_Feature_MySQL_5.6_Jimmy.pdf
MySQL :: MySQL 5.7 Reference Manual :: 14.6.11 Configuring InnoDB Purge Scheduling

i
n both versions is the same version mariadb 10.2.8
thanks

 

[cPanelMichael]

Hello @Mayc,

I believe the processes you noted are normal with MariaDB 10.2. Are you experiencing any actual problems, or were you simply concerned about the name of the processes?

Thank you.

 

[mamati.yazdanbakhsh]

What are the MySQL versions on the two different servers? Are you seeing any issues from these processes? I don't believe there should be any concern or issue with these processes. I believe this is a new threaded purge feature in MySQL(see slide 13):
https://www.mysql.com/news-and-events/events/VDD-MySQL-July13/New_InnoDB_Feature_MySQL_5.6_Jimmy.pdf
MySQL :: MySQL 5.7 Reference Manual :: 14.6.11 Configuring InnoDB Purge Scheduling

Hello,

we have this problem, too on more than 20 servers. please check this photo




it made our servers slow. processes on the accounts made lots of Insoluble problems.

do you have any solution to fix it?

thank you.

 

[cPRex]

@mamati.yazdanbakhsh - can you send me the output of this command on your system?

cat /etc/my.cnf

 

[mamati.yazdanbakhsh]

yes sure

 

[mamati.yazdanbakhsh]

@mamati.yazdanbakhsh - can you send me the output of this command on your system?

cat /etc/my.cnf

thanks for help

 

[cPRex]

That's pretty short, and nothing in there looks obviously wrong to me.

Since those processes aren't related to the cPanel tools but to how MariaDB handles the database information, you may want to read through this guide to see if that can be further optimized:

InnoDB Purge

When a transaction updates a row in an InnoDB table, InnoDB's MVCC implementation keeps old versions of the row in the InnoDB undo log. The old versions are kept at least unt...

mariadb.com