indeedeng / indeedeng/iwf

IWF-350: Sticky state execution: use previous worker instance

Open
#518 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
661
Forks
63
PR merge metrics
No merged PRs in 30d

Description

In SDK, worker service will optionally take in a url of the current instance. Then state options will allow setting a flag that the state execution will try to use the same worker instance as the previous state execution. When enabled, SDK will also send over the worker url for executing the state.

This feature should be used together with the failure recovery feature— it’s possible that the instance got killed and the processing may need to be started over.

Contributor guide

Open the contributing guide

Research direction

No files or tests are named. Start by locating the SDK worker service and state-options entry points, then read the existing failure-recovery feature because this work is intended to be used with it. Done means state execution can optionally reuse the previous worker instance and pass its worker URL, while recovery handles an instance that was killed.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
distributed-systems
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.