Hyper Crashes Cause Other Processes on the Same Node to Unexpectedly Restart

Published: 26 Jun 2019
Last Modified Date: 10 Jul 2019


When a Hyper process quits unexpectedly, it causes other processes on the same node to restart. Some processes, including Backgrounder, can become stalled or hung in the middle of that restart, and become fully unavailable.

Additionally, you can identify this issue with the following steps:

1. Multiple processes restart at about the same time on the same node, often with exit code 130. For example:
2019-05-03 08:49:56.982 -0700  Thread-341 : INFO  com.tableausoftware.process.win32.Win32SystemProcess - Process [38732] exited with code [130].

2. The first of these will be the Hyper process. Note that the only process that Hyper should be restarting if it quits unexpectedly is Hyper itself.
3. Some processes, including Backgrounder, may appear hung or unavailable and unable to be stopped or started. Restarting Tableau Server does not resolve this behavior.


Tableau Server 10.5.0 -10.5.16, 2018.1.0 - 2018.1.13, 2018.2.0 - 2018.2.10, 2018.3.0 - 2018.3.7, 2019.1.0 - 2019.1.4, 2019.2.0


This behavior is related to a known issue (ID: 921509) that is resolved in later versions of Tableau Server.
Did this article resolve the issue?