Automatic restarts for Containers and Executables
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- go, kubernetes
- Domain
- devops, infrastructure
Research direction
No files, tests, or entry points are identified in the issue. Start by reviewing the Container and Executable dependency-service abstractions and the container orchestrator layer, then define restart and backoff behavior; done would require an agreed design and implementation scope.
Written by the indexing model from the issue text.
Description
Motivation
There are cases when a Container or Executable used as a dependency service is not as resilient to transient errors as one would like it to be. In those cases an automatic restart upon failure is a big boost to developer productivity.
Initial design thoughts
If we do this, we should be very careful about avoiding thrashing, i.e. restarting in a tight loop. K8s does it well with "exponential backoff" for repeatedly failing restarts.
For containers we might be able to leverage what the container orchestrator supports, but the support may vary from orchestrator to orchestrator, so DCP might need to backfill in some cases and we might model the restart support as optional in our container orchestrator abstraction layer.
- Dominant language
- Go
- Stars
- 191
- Forks
- 26
- Avg merge
- 22h 49m
- Merged PRs (30d)
- 23
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
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.
More from microsoft/dcp
-
Add application iconOpen
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
microsoft/dcp#286 · 6 comments · 1 assignee ·
Maintainers usually reply within 1 day
-
Disable DeleteCollection for DCP resourcesPossibly taken @TJ2005 claimed this 2 days ago. Open
Difficulty 3/5 1-2 days Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
microsoft/dcp#206 · 2 comments · 1 reaction ·
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
Maintainers usually reply within 1 day
-
bug go
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
genkit-ai/genkit#6761 · 1 comment ·
Maintainers usually reply within 2 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 87/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
github/github-mcp-server#3475 ·
Maintainers usually reply within 4 days