Pivotal Knowledge Base

Follow

GPTEXT Instance failed due to "Java heap space" Error

Environment

 Product  Version
 GPTEXT  1.3.x
 OS  RHEL 5.x, 6.x

Symptom

GPTEXT instance failed and in the related Greenplum segment pg logs we see the following error message:

"XX000","Error sending data.  java.lang.OutOfMemoryError: Java heap space (solr_curl.c:826)  (seg69 slice5 sdw12:40003 pid=29044) (cdbdisp.c:1326)",,,,,,"SELECT * FROM gptext.index(TABLE(
"Master unable to connect to seg0 sdw1:40000 with options gpqeid=855649;545598006163732;false options=' -c gp_segment=0 -c gp_qd_hostname

Resolution

This behavior is a known issue in GPTEXT 1.x. It is caused when the solr instance runs out of memory due to the Java heap exhaustion during usage spikes. This issue is related to JDK1.6 (Used by GPTEXT 1.x). In GPTEXT 2.x (Based on JDK 1.8), this issue no longer exists. If the XMX parameter is already set high enough (Like 4GB), then there are two solutions to fix this issue:

  • If you prefer not to upgrade GPTEXT, then restarting the GPTEXT cluster is the only option
         gptext-stop (possibly gptext-stop -f)
         gptext-start
  • If possible, upgrade to GPTEXT v2.x; it is recommended solution 

Additional Information

To learn how to setup the XMX parameter of solr process, please refer to this link.

 

 

Comments

Powered by Zendesk