StackStorm / StackStorm/st2

Stackstorm action runner does not return / complete - hangs and process is defunct

Open
#5,300 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Docker K8s stale
Dominant language
Python
Stars
6.5k
Forks
787
PR merge metrics
No merged PRs in 30d

Description

When running an action that makes an internal HTTP call (from inside python with requests) that returns a lot of data. The called service is completing and returning HTTP payload over the network (we wiresharked). The action process (we think ?) (after about 15 seconds after the HTTP server returns its data) goes to "defunct" state. The parent process of the action process is the main action runner process.
The core.http action works for same call ; we cannot use it because it will publish the output to the workflow and that is too much data to be in the workflow context due to Mongo db driver/performance issues.

st2 3.4.1, on Python 3.6.8
Running in Docker & Kubernetes
OS is (cat/etc/os-release):
NAME="CentOS Linux"
VERSION="8"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="8"
PLATFORM_ID="platform:el8"
PRETTY_NAME="CentOS Linux 8"

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The report names the action runner, core.http action, Python requests, Docker/Kubernetes, and MongoDB, but no source file or test. Start by reproducing an action that makes an internal HTTP request returning a large payload, then trace the action runner and parent/child process behavior. Done means the action completes without becoming defunct or hanging, while avoiding oversized workflow context.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, kubernetes, mongodb, python
Domain
backend, devops
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.