Bug 1506600

Summary:	openmpi-1.10 shows warnings for NUMA support however openmpi-1.8 works fine.
Product:	Red Hat Enterprise Linux 6	Reporter:	Vishal Pakolu <vpakolu>
Component:	openmpi	Assignee:	John Feeney <jfeeney>
Status:	CLOSED WONTFIX	QA Contact:	Infiniband QE <infiniband-qe>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.9	CC:	bhu, rdma-dev-team
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-10-26 17:46:06 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Vishal Pakolu 2017-10-26 12:01:21 UTC

Description of problem:

Facing issues with openmpi-1.10 receiving warning messages, however same behavior is not shown by openmpi-1.8

--------------------------------------------------------------------------
WARNING: a request was made to bind a process. While the system
supports binding the process itself, at least one node does NOT
support binding memory to the process location.

  Node:  inbansv0053

This usually is due to not having the required NUMA support installed
on the node. In some Linux distributions, the required support is
contained in the libnumactl and libnumactl-devel packages.
This is a warning only; your job will continue, though performance may be degraded.
--------------------------------------------------------------------------

Version-Release number of selected component (if applicable):
 
openmpi-1.10


How reproducible:

Reproducible on RHEL 6.9 with openmpi-1.10

Steps to Reproduce:

The MPI PingPong test has been taken from:

https://raw.githubusercontent.com/wesleykendall/mpitutorial/gh-pages/tutorials/mpi-send-and-receive/code/ping_pong.c

mpicc is contained in the devel RPM. The packages numactl and numactl-devel should be installed.

Make sure to use mpicc from OpenMPI 1.10 to build the program:

$ /usr/lib64/openmpi-1.10/bin/mpicc -o ping_pong ping_pong.c

Make sure it is linked with OpenMPI 1.10 library:

maus@inbansv0053 ~ $ ldd ping_pong
        linux-vdso.so.1 =>  (0x00007ffd185f4000)
        libmpi.so.12 => /usr/lib64/openmpi-1.10/lib/libmpi.so.12 (0x000000305ae00000) # <--------- OpenMPI 1.10 library
[...]

After this step run mpirun (make sure to use the binary from OpenMPI 1.10), substitutes "inbansv0053" with your hostname:

 /usr/lib64/openmpi-1.10/bin/mpirun -H inbansv0053,inbansv0053  --mca btl ^tcp --bind-to core /home/maus/ping_pong
--------------------------------------------------------------------------
WARNING: a request was made to bind a process. While the system
supports binding the process itself, at least one node does NOT
support binding memory to the process location.

  Node:  inbansv0053

This usually is due to not having the required NUMA support installed
on the node. In some Linux distributions, the required support is
contained in the libnumactl and libnumactl-devel packages.
This is a warning only; your job will continue, though performance may be degraded.
--------------------------------------------------------------------------
0 sent and incremented ping_pong_count 1 to 1
0 received ping_pong_count 2 from 1
Actual results:


Expected results:

Runs without warning message.

Additional info:

Comment 2 Beth Uptagrafft 2017-10-26 17:46:06 UTC

Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the
Production 3 Phase, Critical impact Security Advisories (RHSAs) and
selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as
they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase
and will be marked as CLOSED/WONTFIX. If this remains a critical
requirement, please contact Red Hat Customer Support to request
a re-evaluation of the issue, citing a clear business justification. Note
that a strong business justification will be required for re-evaluation.
Red Hat Customer Support can be contacted via the Red Hat Customer Portal
at the following URL:

https://access.redhat.com/