You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by "jokester (via GitHub)" <gi...@apache.org> on 2026/06/15 05:30:50 UTC
Re: [D] Error : superset_app : worker(pid) was sent SIGKILL! perhaps out of memory [superset]
GitHub user jokester added a comment to the discussion: Error : superset_app : worker(pid) was sent SIGKILL! perhaps out of memory
The "perhaps out of memory" is but a guess of the cause. Likely hardcoded in web server for SIGKILL.
In my own case which guided me to this thread: I had a evaluation config running under guvicorn and with no redis or celery . Mine repeatedly prints the following, and the cause is likely a timeout, rather than OOM:
> [2026-06-15 14:24:03 +0900] [249632] [CRITICAL] WORKER TIMEOUT (pid:3316443)
> [2026-06-15 14:24:04 +0900] [249632] [ERROR] Worker (pid:3316443) was sent SIGKILL! Perhaps out of memory?
> [2026-06-15 14:24:04 +0900] [3328562] [INFO] Booting worker with pid: 3328562
GitHub link: https://github.com/apache/superset/discussions/31299#discussioncomment-17303685
----
This is an automatically sent email for notifications@superset.apache.org.
To unsubscribe, please send an email to: notifications-unsubscribe@superset.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org