GPE FAQ

The GPE (Graph Processing Engine) is the main Engine component of TigerGraph, responsible for receiving queries from RESTPP, updating the graph data, and retrieving data. The GPE is the heart of TigerGraph.

GPE Crash

Possible issue

On versions prior to 3.2.0 the following scenario can occur. A large data update is sent to the GPE which is not able to process it quickly. After time, if the Kafka queue that the GPE receives update from exceeds 2 GB, the GPE will crash.

Suggested troubleshooting methods

Check process status using gadmin status and review logs using gadmin log gpe if the GPE crashes. Usually with this scenario, the GPE will crash again after it is started and before it finishes warming up.

Recommended solution

  1. Temporary:

    • Reduce frequency of data updates/posts so that the GPE has time to process them as they come in

    • Avoid extremely large data updates, especially on one single vertex

    • Spread data updates out over time

    • Use gadmin reset -y to clear the Kafka queue and bring the system back up

  2. Recommended

    • Upgrade to version 3.2 which has added safe handling of this scenario.