microsoft / microsoft/durabletask-mssql
Prevent termination of pods with long-running functions using KEDA
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 105
- Forks
- 36
- PR merge metrics
- No merged PRs in 30d
Description
What is the general guidance for preventing termination of pods with long-running functions while using KEDA?
In testing, I've seen that during a scale down, the HPA can terminate a pod that is still running an orchestration/activity function.
This behavior is documented here: https://keda.sh/docs/1.4/concepts/scaling-deployments/#long-running-executions
What's the recommended method to prevent this from occurring?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No repository files or tests are named. Start with the linked KEDA documentation on long-running executions and review how this Durable Functions SQL provider is deployed with KEDA; done means documenting a repository-specific, recommended way to avoid terminating pods during active orchestration or activity functions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- devops, infrastructure
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100