nebari-dev / nebari-dev/nebari-docs
[DOC] - FAQ - Dying nodes on AWS due to AZRebalance
Open
Nobody has claimed this yet.
area: documentation 📖
good first issue
impact: low 🟩
- Dominant language
- No language data
- Stars
- 21
- Forks
- 40
- Avg merge
- 19h 50m
- Merged PRs (30d)
- 6
Description
Preliminary Checks
- This issue is not a question, feature request, RFC, or anything other than a bug report. Please post those things in GitHub Discussions: https://github.com/nebari-dev/nebari/discussions
Summary
We have an FAQ topic on how to resolve this in the old docs that needs to be migrated over.
Steps to Resolve this Issue
add faq item
Contributor 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.
Research direction
Start by reading the linked old FAQ entry about AWS AZRebalance and dying Dask nodes. Then locate the corresponding FAQ section in this documentation repository and migrate the topic, including the relevant guidance and image if needed. Done means the FAQ item is present in the new docs and renders correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100