"InnoDB: Failed to set NUMA memory policy" on 32-bit hosts

[Laurynas Biveinis]

PS 5.6 trunk:

sys_vars.innodb_buffer_pool_populate_basic w4 [ fail ] Found warnings/errors in server log file!
        Test ended at 2016-08-22 08:52:08
line
2016-08-22 15:52:07 30010 [Warning] InnoDB: Failed to set NUMA memory policy to MPOL_INTERLEAVE (error: Function not implemented).
2016-08-22 15:52:07 30010 [Warning] InnoDB: Failed to set NUMA memory policy of buffer pool page frames to MPOL_INTERLEAVE (error: Function not implemented).
2016-08-22 15:52:07 30010 [Warning] InnoDB: Failed to set NUMA memory policy to MPOL_DEFAULT (error: Function not implemented).
^ Found warnings in /mnt/workspace/percona-server-5.6-trunk/BUILD_TYPE/release/Host/ubuntu-precise-32bit/build/mysql-test/var/4/log/mysqld.1.err
ok

It looks like NUMA calls on 32-bit hosts return ENOSYS. Probably the CMake check should be made aware of this and not compile in NUMA support on such system.

[Laurynas Biveinis (laurynas-biveinis)]

OTOH, that's too much of a requirement for a build system. Suppressing the warning is enough.

[Laurynas Biveinis (laurynas-biveinis)]

     https://github.com/percona/percona-server/pull/890
     https://github.com/percona/percona-server/pull/891

[Thomas Deutschmann (whissi)]

Oh, you already fixed the problem.

I was going to report this today. We track this as https://bugs.gentoo.org/show_bug.cgi?id=584880

Just saying that I hit the problem on x64 when CONFIG_NUMA is not set in kernel. For me it looked like you missed to source "have_numa.inc" but your fix is different.

[Shahriyar Rzayev (rzayev-sehriyar)]

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PS-3522