In a metadata server cluster, you might encounter an issue in which an individual metadata server node is not able to rejoin the cluster quorum. When you encounter this issue, the SAS^® Management Console report shows the MetadataServer cluster status as Not Running.

This issue is likely to occur when a virtual machine administrator disables and enables the network adapters while the metadata server (cluster) is running. When network adapters are disabled, the metadata server cluster nodes lose quorum with each other. Later, when the network is enabled, the nodes should reconnect automatically. However, in the case of a dynamic Domain Name System (DNS), the nodes are unable to resolve host names and IP addresses because the /etc/resolv.conf file containing the name resolution instructions is rewritten. The nodes are not able to rejoin the MetadataServer cluster quorum. Disabling network adapters on the metadata server cluster is disruptive to a running SAS environment.

To work around this issue, use one of the following strategies:

• Statically define all host names and IP addresses in the /etc/hosts file for all SAS nodes.
• Do not use NetworkManager, which rewrites the /etc/resolv.conf file, but configure the name service cache daemon (NSCD) service. See your Linux operating system manual for more information.
• Restart the metadata server nodes that are in the Not Running state one at a time.

Click the Hot Fix tab in this note to access the hot fix for this issue.

Operating System and Release Information

A fix for this issue for SAS Threaded Kernel Core Routines 9.4_M5 is available at:

A fix for this issue for SAS Threaded Kernel Core Routines 9.4_M4 is available at:

A fix for this issue for SAS Threaded Kernel Core Routines 9.4_M3 is available at: