Azure / Azure/azure-functions-host
Autoheal
Open
enhancement
- Dominant language
- C#
- Stars
- 2k
- Forks
- 482
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 38
Description
I've seen a few issues (I believe they're all related to port exhaustion) which prevent the runtime from starting and require a restart to resolve.
We should be able to set autoheal rules to restart any apps which are constantly returning 503s. The scale controller pings should trigger these for even non-http apps.
Contributor guide
Research direction
Start by tracing the runtime's handling of repeated 503 responses and the scale controller pings mentioned in the issue. Determine where autoheal rules belong and how non-HTTP apps would be covered; done means a defined restart policy is implemented and verified for both HTTP and non-HTTP apps.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, csharp
- Domain
- backend, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100