What Should I Do If the Impalad Node Continuously Reports Full GC and the SQL Statement Is Always in the Created State When the xmx Memory of Impalad Is Less Than That of Catalog?

Question

The xmx memory of Impalad is less than that of Catalog. When Catalog runs for a long time, the memory exceeds the xmx memory of Impalad. The Impalad node continuously reports Full GC, metadata is not completely synchronized, and SQL statements are always in the "Created" state. How do I solve this problem?

Answer

Increase the Impalad xmx memory to be no less than the Catalog xmx memory.

1. Log in to FusionInsight Manager, choose Cluster > Services > Impala, and click Configurations and then All Configurations. In the tab, choose Catalog(Role) > Environment. Check and record the value of xmx in the IMPALA_GC_OPTS parameter.
2. Choose Cluster > Services > Impala and click Configurations and then All Configurations. In the tab, choose Impalad(Role) > Environment. Change the value of xmx in the IMPALA_GC_OPTS parameter. Ensure the memory size is greater than or equal to the catalog xmx memory. Save the configuration and restart the instance whose configuration expired.