I believe that MariaDB documentation about innodb_numa_interleave is wrong/outdated.

https://mariadb.com/kb/en/library/xtradbinnodb-server-system-variables/#innodb_numa_interleave

"Requires that MariaDB be compiled on a NUMA-enabled Linux system."

This was the same behaviour as in MySQL pre 5.6.27 or so... But nowadays mySQL 5.7 has just the option innodb_numa_interleave. No compilation is needed any more!

I do not have NUMA hardware but I just tried today in my.cnf follow by a restart and I get a message in MariaDB error log as follows:

2018-06-13 18:49:00 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2018-06-13 18:49:00 0 [Note] InnoDB: Setting NUMA memory policy to MPOL_INTERLEAVE
2018-06-13 18:49:00 0 [Note] InnoDB: Setting NUMA memory policy to MPOL_DEFAULT
2018-06-13 18:49:00 0 [Note] InnoDB: Completed initialization of buffer pool

So I strongly believe that MariaDB 10.3 behaves the same as MySQL 5.7. Thus IMHO documentation should honor this new behaviour (which is quite useful for enterprise grade serves)

See also: https://jira.mariadb.org/browse/MDEV-10829