On Tue, 25 Sep 2018 10:48:01 +0200
Kenneth Penza <kpenza@gmail.com> wrote:

> Good morning,


Good morning,

Thanks for the detailed bug report. As the contributor of this feature
I'm happy to try to work this out. First I'll reassure you that the
WARNING is simply that, there's no negative impacts form this apart
from any unexpected core dump will include the large pages as it failed
to to mark them as don't dump.

A couple of small clarifying questions to start:

Do you have THP enabled?
$ cat /proc/sys/vm/nr_hugepages

What kernel version / architecture?
$ uname -a

What huge page size /  current allocation is available?

$ grep ^Huge /proc/meminfo


> I am currently running RHEL 7.5 and MariaDB 10.3.9. After setting
> "large_pages=on"  I noticed that MariaDB is reporting an error on
> startup and shutdown as per below output.
>
> To use large pages I
> modified /etc/sysctl.conf, /etc/security/limits.conf and the systemd
> unit file. By monitoring /proc/meminfo I verified that largepage are
> being used.
>
> Configuration:
>
> mysqld would have been started with the following arguments:
> --port=3306 --socket=/var/lib/mysql/mysql.sock --thread_stack=256K
> --large_pages=on --key_buffer_size=16K --max_allowed_packet=512M
> --table_open_cache=32 --sort_buffer_size=512K --net_buffer_length=8K
> --read_buffer_size=256K --read_rnd_buffer_size=256K --slow_query_log=1
> --slow_query_log_file=mysql-slow.log --long_query_time=0.1
> --log-queries-not-using-indexes=on --thread_handling=pool-of-threads
> --thread_pool_idle_timeout=60 --thread_pool_max_threads=1000
> --thread_pool_size=8 --innodb_buffer_pool_size=256M
> --innodb_strict_mode=1 --innodb_file_per_table=1
> --innodb_flush_method=O_DIRECT --innodb_log_files_in_group=4
> --innodb_log_file_size=50331648 --innodb_undo_logs=128
> --innodb_undo_tablespaces=8 --slow_query_log=1
> --slow_query_log_file=mysql-slow.log --long_query_time=30
> --log-queries-not-using-indexes=off --log_bin=mariadblog
> --binlog_format=ROW --binlog_row_image=MINIMAL
> --max_binlog_size=10240000 --expire_logs_days=1 --server-id=1
> --innodb_flush_log_at_trx_commit=1 --sync_binlog=1
> --relay-log=mariadb-relay-bin --performance_schema=off
> --histogram_size=255 --histogram_type=SINGLE_PREC_HB
> --use_stat_tables=preferably --optimizer_use_condition_selectivity=4
>
> Startup messages:
>
> Sep 25 10:40:53 srv1 mysqld: 2018-09-25 10:40:52 0 [Note] InnoDB:
> Opened 8 undo tablespaces
> Sep 25 10:40:53 srv1 mysqld: 2018-09-25 10:40:53 0 [Warning] InnoDB:
> Failed to set memory to DODUMP: Invalid argument ptr 0x2aaac5400000
> size 2097152 Sep 25 10:40:53 srv1 mysqld: 2018-09-25 10:40:53 0
> [Note] InnoDB: 128 out of 128 rollback segments in 8 undo tablespaces
> are active.
>
> Shutdown messages:
>
> Sep 25 10:41:18 srv1 mysqld: 2018-09-25 10:41:18 0 [Note] InnoDB:
> Buffer pool(s) dump completed at 180925 10:41:18
> Sep 25 10:41:19 srv1 mysqld: 2018-09-25 10:41:19 0 [Warning] InnoDB:
> Failed to set memory to DODUMP: Invalid argument ptr 0x2aaac3400000
> size 33554432 Sep 25 10:41:19 srv1 mysqld: 2018-09-25 10:41:19 0
> [Note] InnoDB: Shutdown completed; log sequence number 1522725;
> transaction id 22
>
> Do you have ideas on what is causing "InnoDB: Failed to set memory to
> DODUMP: Invalid argument ptr .. " warning?



>
> Kenneth