Help Center/ MapReduce Service/ Component Operation Guide (LTS)/ Using HetuEngine/ Common Issues About HetuEngine/ What Do I Do If Error "Encountered too many errors" Is Reported During HetuEngine SQL Execution?
Updated on 2024-12-13 GMT+08:00
View PDF
Share

What Do I Do If Error "Encountered too many errors" Is Reported During HetuEngine SQL Execution?

Question

The following error is reported during the execution of HetuEngine service SQL statements:

Encountered too many errors talking to a worker node. The node may have crashed or be under too much load. This is probably a transient issue, so please retry your query in a few minutes

Answer

Possible causes:

  • Some Worker nodes are faulty, for example, the network is abnormal or the process memory usage is high.
  • The worker node is overloaded, memory is used up (OOM), and the worker node cannot provide services.
  • The worker node automatically restarts due to GC.

Solution:

  • For faulty worker node:

    If errors are reported on the same worker node at different time, check the node. For example, check the network connection and memory usage.

  • High worker node load and GC
    1. Log in to FusionInsight Manager as a user who can access the HetuEngine web UI and choose Cluster > Services > HetuEngine. The HetuEngine service page is displayed.
    2. Click Dashboard. In the Basic Information area, click the link next to HSConsole WebUI. The HSConsole page is displayed.
    3. On the Compute Instances page, expand the tenant to which the compute instance belongs and ensure that the instance you want to modify is STOPPED.
    4. Locate the row that contains the tenant to which the compute instance belongs, and click Configure in the Operation column. The Configure Instance tab is displayed.
      1. Increase the memory size of a worker in a compute instance.

        In the configuration of a single compute instance, increase the value of Container Memory (MB) of Worker Container Resource Configuration and the value of -Xmx in JVM.

      2. Limit the memory usage of a query on a worker.

        In the Custom Configuration area, click Add to add the query.max-memory-per-node parameter twice for coordinator.config.properties and worker.config.properties, respectively. Set them to a value less than 70% of the -Xmx in JVM.

    5. Click OK and restart the compute instance.