"Unexpected internal error (tuplestorenew.c:407)" Displayed When Greenplum Is Running SQL Statements

Symptom

Before KAEzip is enabled, the messages "Unexpected internal error (tuplestorenew.c:407)", "HINT: Process x will wait for gpdebuglinger=120 seconds before termination", and "Note that its locks and other resources will not be released until then" are displayed when Greenplum is running SQL statements.

Key Process and Cause Analysis

The possible causes are as follows:

• Insufficient resources. You need to check system resources (such as memory, CPU, and drive I/O) and make adjustments as required.
• Interference caused by external factors, such as network problems, which may need to be optimized.

Conclusion and Solution

• For insufficient resources, perform the following steps:
  1. Disable resource_scheduler and gp_resqueue_priority of Greenplum at the same time:

     gpconfig -c resource_scheduler -v off
     gpconfig -c gp_resqueue_priority -v off

  2. Run the SQL statement again.
  3. If the fault persists, enable the deadlock detector parameter gp_enable_global_deadlock_detector of Greenplum:

     gpconfig -c gp_enable_global_deadlock_detector -v on

  4. Run the SQL statement again.
• For network problems, perform the following steps:
  1. Use a high-speed NIC with a preferred bandwidth of 25,000 MB/s or higher.
  2. Run the SQL statement again.