Problem Note 59039: The SAS® import procedure causes an out of memory condition, corruption of metadata, or a loss of quorum for a clustered SAS® Metadata Server
A problem occurs when the Import SAS Package wizard is invoked in a clustered Metadata Server environment. The master server is unable to complete synchronization with the slave nodes, which might cause an out of memory condition, corruption of metadata, or a loss of quorum. The problem might occur even with relatively small import packages in the 30 MB size range.
SPK files are created and used by the Import SAS Package and Export SAS Package promotion tools, which are available in SAS® Management Console as well as from the command-line as batch scripts. For details about these tools, see the "Introduction to the Promotion Tools" section in SAS(R) 9.4 Intelligence Platform: System Administration Guide, Fourth Edition.
When you encounter this problem, the SAS Metadata Server log shows messages similar to these:
WARN [00000667] 35:a12345 - JnlfileWrite: Used Big compressor to compress journal entry from size 2498171728
to 80179669 at position 24183 (0x5e77):
WARN [00000667] 35:a12345 - There is insufficient memory available to send an update to a slave node at this
time so we must wait a short while until some becomes available.
WARN [00000667] 35:a12345 - Sufficient memory to send an update to a slave node did not become available in
time. The node will have to be resynchronized later.
ERROR [00000667] 35:a12345 - Insufficient memory
ERROR [00000667] 35:a12345 - CRITICAL ERROR encountered queueing journal entry to be sent to the slave nodes.
In most cases, UNIX systems are more susceptible to the problem than Microsoft Windows systems. This difference is a result of how each operating system stores threaded-kernel characters (TKChars). Windows uses two bytes to store TKChars, whereas UNIX uses four bytes.
To circumvent the problem, perform the import process with smaller SPK files or select a subset of objects to import from the larger SPK files.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
SAS System | SAS Metadata Server | z/OS | 9.4_M3 | 9.4_M4 | 9.4 TS1M3 | 9.4 TS1M4 |
Microsoft® Windows® for x64 | 9.4_M3 | 9.4_M4 | 9.4 TS1M3 | 9.4 TS1M4 |
Microsoft Windows 8 Enterprise 32-bit | 9.4_M3 | 9.4_M4 | 9.4 TS1M3 | 9.4 TS1M4 |
Microsoft Windows 8 Enterprise x64 | 9.4_M3 | 9.4_M4 | 9.4 TS1M3 | 9.4 TS1M4 |
Microsoft Windows 8 Pro 32-bit | 9.4_M3 | 9.4_M4 | 9.4 TS1M3 | 9.4 TS1M4 |
Microsoft Windows 8 Pro x64 | 9.4_M3 | 9.4_M4 | 9.4 TS1M3 | 9.4 TS1M4 |
Microsoft Windows 8.1 Enterprise 32-bit | 9.4_M3 | 9.4_M4 | 9.4 TS1M3 | 9.4 TS1M4 |
Microsoft Windows 8.1 Enterprise x64 | 9.4_M3 | 9.4_M4 | 9.4 TS1M3 | 9.4 TS1M4 |
Microsoft Windows 8.1 Pro 32-bit | 9.4_M3 | 9.4_M4 | 9.4 TS1M3 | 9.4 TS1M4 |
Microsoft Windows 8.1 Pro x64 | 9.4_M3 | 9.4_M4 | 9.4 TS1M3 | 9.4 TS1M4 |
Microsoft Windows 10 | 9.4_M3 | 9.4_M4 | 9.4 TS1M3 | 9.4 TS1M4 |
Microsoft Windows Server 2008 | 9.4_M3 | 9.4_M4 | 9.4 TS1M3 | 9.4 TS1M4 |
Microsoft Windows Server 2008 R2 | 9.4_M3 | 9.4_M4 | 9.4 TS1M3 | 9.4 TS1M4 |
Microsoft Windows Server 2008 for x64 | 9.4_M3 | 9.4_M4 | 9.4 TS1M3 | 9.4 TS1M4 |
Microsoft Windows Server 2012 Datacenter | 9.4_M3 | 9.4_M4 | 9.4 TS1M3 | 9.4 TS1M4 |
Microsoft Windows Server 2012 R2 Datacenter | 9.4_M3 | 9.4_M4 | 9.4 TS1M3 | 9.4 TS1M4 |
Microsoft Windows Server 2012 R2 Std | 9.4_M3 | 9.4_M4 | 9.4 TS1M3 | 9.4 TS1M4 |
Microsoft Windows Server 2012 Std | 9.4_M3 | 9.4_M4 | 9.4 TS1M3 | 9.4 TS1M4 |
Windows 7 Enterprise 32 bit | 9.4_M3 | 9.4_M4 | 9.4 TS1M3 | 9.4 TS1M4 |
Windows 7 Enterprise x64 | 9.4_M3 | 9.4_M4 | 9.4 TS1M3 | 9.4 TS1M4 |
Windows 7 Home Premium 32 bit | 9.4_M3 | 9.4_M4 | 9.4 TS1M3 | 9.4 TS1M4 |
Windows 7 Home Premium x64 | 9.4_M3 | 9.4_M4 | 9.4 TS1M3 | 9.4 TS1M4 |
Windows 7 Professional 32 bit | 9.4_M3 | 9.4_M4 | 9.4 TS1M3 | 9.4 TS1M4 |
Windows 7 Professional x64 | 9.4_M3 | 9.4_M4 | 9.4 TS1M3 | 9.4 TS1M4 |
Windows 7 Ultimate 32 bit | 9.4_M3 | 9.4_M4 | 9.4 TS1M3 | 9.4 TS1M4 |
Windows 7 Ultimate x64 | 9.4_M3 | 9.4_M4 | 9.4 TS1M3 | 9.4 TS1M4 |
64-bit Enabled AIX | 9.4_M3 | 9.4_M4 | 9.4 TS1M3 | 9.4 TS1M4 |
64-bit Enabled Solaris | 9.4_M3 | 9.4_M4 | 9.4 TS1M3 | 9.4 TS1M4 |
HP-UX IPF | 9.4_M3 | 9.4_M4 | 9.4 TS1M3 | 9.4 TS1M4 |
Linux for x64 | 9.4_M3 | 9.4_M4 | 9.4 TS1M3 | 9.4 TS1M4 |
Solaris for x64 | 9.4_M3 | 9.4_M4 | 9.4 TS1M3 | 9.4 TS1M4 |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
When large jobs are imported, the import creates journal entries that might exceed the memory available or cause Metadata Server slave node synchronization to fail.
Type: | Problem Note |
Priority: | high |
Date Modified: | 2016-10-19 13:00:37 |
Date Created: | 2016-09-25 14:30:50 |