<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>article Qlik Catalog Data Loads fail due Out of Memory Error in Official Support Articles</title>
    <link>https://community.qlik.com/t5/Official-Support-Articles/Qlik-Catalog-Data-Loads-fail-due-Out-of-Memory-Error/ta-p/2145057</link>
    <description>&lt;P&gt;Qlik Catalog Data loads fail to complete due to an &lt;FONT color="#339966"&gt;&lt;STRONG&gt;out of memory&lt;/STRONG&gt;&lt;/FONT&gt; error.&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;The issue can be addressed by either increasing memory on the host running Qlik Catalog and engine or by decreasing the number of concurrent loads Catalog will process (32 by default). You may need to do both.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;H3&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Resolution&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H3&gt;
&lt;P&gt;Decrease&lt;SPAN&gt;&amp;nbsp;the number of concurrent loads to 4.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;The setting is changed in the &lt;FONT face="courier new,courier"&gt;core_env.properties&lt;/FONT&gt; file located in the directory:&amp;nbsp;&lt;FONT face="courier new,courier"&gt;QDC_HOME/&amp;lt;Tomcat&amp;gt;/conf/core_env.properties&lt;/FONT&gt;.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;A Tomcat restart is required after making the change in the&amp;nbsp;&lt;/SPAN&gt;&lt;FONT face="courier new,courier"&gt;core_env.properties&lt;/FONT&gt;&lt;SPAN&gt; file.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Make the change when no loads are running. Find and edit the following (do not add a new entry):&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;&lt;FONT face="courier new,courier"&gt;&lt;SPAN&gt;# Number of Java threads in pool used for each of loading data, prepare and publish.&lt;/SPAN&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;&lt;SPAN&gt;# Restart required. Default: 32&lt;/SPAN&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;&lt;SPAN&gt;hadoop.job.poolsize=4&lt;/SPAN&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;If the loads are successful, increase the count gradually and continue testing.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;If it is easy to provision more RAM, consider doing so.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H3&gt;&lt;STRONG&gt;&lt;FONT color="#339966"&gt;Cause&lt;/FONT&gt; &lt;/STRONG&gt;&lt;/H3&gt;
&lt;P&gt;&lt;SPAN&gt;Qlik Catalog uses the "engine" container to convert QVDs to CSVs (in order to sample and profile the data). The issue is that engine is running out of memory attempting to concurrently process several QVDs. Sometimes engine gracefully handles the memory exhaustion and returns an error to Qlik Catalog. Other times engine crashes and the container is restarted. In both cases, the job status is FAILED in Qlik Catalog.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H4&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Environment&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H4&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;LI-PRODUCT title="Qlik Catalog" id="qlikCatalog"&gt;&lt;/LI-PRODUCT&gt;&amp;nbsp;&lt;/LI&gt;
&lt;/UL&gt;</description>
    <pubDate>Thu, 14 Dec 2023 14:48:20 GMT</pubDate>
    <dc:creator>Gerald_U</dc:creator>
    <dc:date>2023-12-14T14:48:20Z</dc:date>
    <item>
      <title>Qlik Catalog Data Loads fail due Out of Memory Error</title>
      <link>https://community.qlik.com/t5/Official-Support-Articles/Qlik-Catalog-Data-Loads-fail-due-Out-of-Memory-Error/ta-p/2145057</link>
      <description>&lt;P&gt;Qlik Catalog Data loads fail to complete due to an &lt;FONT color="#339966"&gt;&lt;STRONG&gt;out of memory&lt;/STRONG&gt;&lt;/FONT&gt; error.&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;The issue can be addressed by either increasing memory on the host running Qlik Catalog and engine or by decreasing the number of concurrent loads Catalog will process (32 by default). You may need to do both.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;
&lt;H3&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Resolution&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H3&gt;
&lt;P&gt;Decrease&lt;SPAN&gt;&amp;nbsp;the number of concurrent loads to 4.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;The setting is changed in the &lt;FONT face="courier new,courier"&gt;core_env.properties&lt;/FONT&gt; file located in the directory:&amp;nbsp;&lt;FONT face="courier new,courier"&gt;QDC_HOME/&amp;lt;Tomcat&amp;gt;/conf/core_env.properties&lt;/FONT&gt;.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;A Tomcat restart is required after making the change in the&amp;nbsp;&lt;/SPAN&gt;&lt;FONT face="courier new,courier"&gt;core_env.properties&lt;/FONT&gt;&lt;SPAN&gt; file.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Make the change when no loads are running. Find and edit the following (do not add a new entry):&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;&lt;FONT face="courier new,courier"&gt;&lt;SPAN&gt;# Number of Java threads in pool used for each of loading data, prepare and publish.&lt;/SPAN&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;&lt;SPAN&gt;# Restart required. Default: 32&lt;/SPAN&gt;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier"&gt;&lt;SPAN&gt;hadoop.job.poolsize=4&lt;/SPAN&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;If the loads are successful, increase the count gradually and continue testing.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;If it is easy to provision more RAM, consider doing so.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H3&gt;&lt;STRONG&gt;&lt;FONT color="#339966"&gt;Cause&lt;/FONT&gt; &lt;/STRONG&gt;&lt;/H3&gt;
&lt;P&gt;&lt;SPAN&gt;Qlik Catalog uses the "engine" container to convert QVDs to CSVs (in order to sample and profile the data). The issue is that engine is running out of memory attempting to concurrently process several QVDs. Sometimes engine gracefully handles the memory exhaustion and returns an error to Qlik Catalog. Other times engine crashes and the container is restarted. In both cases, the job status is FAILED in Qlik Catalog.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;H4&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Environment&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H4&gt;
&lt;UL&gt;
&lt;LI&gt;&lt;LI-PRODUCT title="Qlik Catalog" id="qlikCatalog"&gt;&lt;/LI-PRODUCT&gt;&amp;nbsp;&lt;/LI&gt;
&lt;/UL&gt;</description>
      <pubDate>Thu, 14 Dec 2023 14:48:20 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Official-Support-Articles/Qlik-Catalog-Data-Loads-fail-due-Out-of-Memory-Error/ta-p/2145057</guid>
      <dc:creator>Gerald_U</dc:creator>
      <dc:date>2023-12-14T14:48:20Z</dc:date>
    </item>
  </channel>
</rss>

