Oracle Linux: How To Disable NUMA At OS Level (Doc ID 2193586.1)

简介: Oracle Linux: How To Disable NUMA At OS Level (Doc ID 2193586.1)

FOR LEGACY GRUB

To disable NUMA, add numa=off to the kernel line in /boot/grub/grub.conf , as follows:

kernel /vmlinuz-2.6.39-400.215.10.el5uek ro root=/dev/VolGroup00/LogVol00 numa=off

Reboot server.

shutdown -r now

Validate NUMA is disabled after server boot successfully.
$ uptime
22:11:10 up 23 days, 3:12, 1 user, load average: 0.00, 0.01, 0.05

cat /proc/cmdline

ro root=/dev/VolGroup00/LogVol00 numa=off <---------- NUMA is disabled

numactl -H

available: 1 nodes (0)
node 0 size: 4195 MB
node 0 free: 3304 MB
node distances:
node 0
0: 10

Also, if NUMA were activated, there would be more than one node listed in the above output.
FOR GRUB2 EFI Boot Loader

To disable NUMA on servers which use the EFI boot loader. GRUB 2 is the default EFI-mode boot loader, so the steps are based on GRUB2.

Take a backup of /etc/default/grub file.
Edit /etc/default/grub file and replace numa=on to numa=off.

vi /etc/default/grub

..
GRUB_CMDLINE_LINUX_DEFAULT="root=LABEL=DBSYS bootarea=dbsys bootfrom=BOOT ro loglevel=7 panic=60 debug pci=noaer log_buf_len=1m nmi_watchdog=0 transparent_hugepage=never rd_NO_PLYMOUTH audit=1 console=tty1 console=ttyS0,115200n8 crashkernel=448M@128M numa=on << -- Replace it as off

Run the following command to rebuild the grub.cfg

grub2-mkconfig -o /boot/efi/EFI/redhat/grub.cfg

Reboot the server to make the changes effect.

Disable Numa on Virtual Machine

vNUMA removes the transparency between the VM and the OS and presents the NUMA architecture directly to the VM’s operating system. It worth mentioning that vNUMA also known as wide NUMA in the industry.

To disable NUMA on Xen Hypervisor it needs downtime.

Backup /etc/xen/xend-config.sxp file.

cp /etc/xen/xend-config.sxp /etc/xen/xend-config.sxp.bkp_default.

Edit /etc/xen/xend-config.sxp file and replace "(vnuma 1)" to "(vnuma 0)"
[root@ VirtualDisks]# vi /etc/xen/xend-config.sxp

# Enable or disable HVM guests seeing an vNUMA topology by default.
(vnuma 0)                       ⇒ 0 Means disabled and 1 means enabled (space is there for (vnuma 0))

Restart Xend service to make the changes effect.
[root@ VirtualDisks]# /etc/init.d/xend restart
Stop/Start the Guest Machines.
[root@ VirtualDisks]# xm stop 0004fb0000060000aa3c75119ef2e544
[root@ VirtualDisks]# xm start 0004fb0000060000aa3c75119ef2e544

Before activity:
[root@ ~]# numactl --hardware
available: 2 nodes (0-1) ⇒ If the number of available nodes is "2 nodes (0-1)" or "8 nodes (0-7)" then NUMA is enabled. If the number of available nodes is "1 nodes (0)" then NUMA is not enabled.
node 0 cpus: 0
node 0 size: 9997 MB
node 0 free: 9879 MB
node 1 cpus: 1
node 1 size: 10078 MB
node 1 free: 10019 MB
node distances:
node 0 1
0: 10 21
1: 21 10

After reboot:
[root@ ~]# numactl --hardware
available: 1 nodes (0)
node 0 cpus: 0 1
node 0 size: 20076 MB
node 0 free: 19897 MB
node distances:
node 0
0: 10

相关文章
|
15天前
|
运维 Oracle 容灾
Oracle dataguard 容灾技术实战(笔记),教你一种更清晰的Linux运维架构
Oracle dataguard 容灾技术实战(笔记),教你一种更清晰的Linux运维架构
|
17天前
|
存储 Linux C语言
Linux:冯·诺依曼结构 & OS管理机制
Linux:冯·诺依曼结构 & OS管理机制
17 0
|
10天前
|
存储 Linux
linux上SVN出现 "Unable to connect to a repository at URL 'svn://xx.xx.xx.xx/xxx' 和 No repository ...
centos上安装了svn, 有时候会不知道什么原因出现客户端小乌龟无法连接或无法提交等情况
22 5
|
17天前
|
Oracle Java 关系型数据库
【服务器】python通过JDBC连接到位于Linux远程服务器上的Oracle数据库
【服务器】python通过JDBC连接到位于Linux远程服务器上的Oracle数据库
19 6
|
17天前
|
Oracle 关系型数据库 Linux
SuSE linux server 11通过SAP来安装oracle11g
SuSE linux server 11通过SAP来安装oracle11g
15 0
|
17天前
|
Linux 调度
Linux定时任务调度--crontab与at
Linux定时任务调度--crontab与at
38 0
|
17天前
|
算法 Linux 调度
根基已筑!Anolis OS 23.1 预览版本搭载 Linux 6.6 内核和工具链升级完成
Anolis OS 23.1 对软件包的选择和组合进行了重新规划与决策,满足更为广泛的应用场景需求。
|
9天前
|
Oracle 关系型数据库 Java
实时计算 Flink版操作报错之读取Oracle数据库时遇到找不到驱动,是什么原因
在使用实时计算Flink版过程中,可能会遇到各种错误,了解这些错误的原因及解决方法对于高效排错至关重要。针对具体问题,查看Flink的日志是关键,它们通常会提供更详细的错误信息和堆栈跟踪,有助于定位问题。此外,Flink社区文档和官方论坛也是寻求帮助的好去处。以下是一些常见的操作报错及其可能的原因与解决策略。
实时计算 Flink版操作报错之读取Oracle数据库时遇到找不到驱动,是什么原因
|
13天前
|
Oracle 关系型数据库 MySQL
实时计算 Flink版操作报错合集之采集oracle的时候报ORA-65040:不允许从可插入数据库内部执行该操作如何解决
在使用实时计算Flink版过程中,可能会遇到各种错误,了解这些错误的原因及解决方法对于高效排错至关重要。针对具体问题,查看Flink的日志是关键,它们通常会提供更详细的错误信息和堆栈跟踪,有助于定位问题。此外,Flink社区文档和官方论坛也是寻求帮助的好去处。以下是一些常见的操作报错及其可能的原因与解决策略。
39 3
|
17天前
|
SQL Oracle 安全
Oracle11g更改数据库名(详细教程)
Oracle11g更改数据库名(详细教程)
23 1