Repository navigation
Conversation
|
🚀 Build success! Latest successful preview: https://preview-557--questdb-documentation.netlify.app/docs/ Commit SHA: cc4d1c7
|
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
sklarsa
force-pushed
the
docs/operator-node-pool-maintenance
branch
from
October 16, 2026 15:24
b6830e2 to
a76d4ad
Compare
sklarsa
marked this pull request as ready for review
October 16, 2026 17:14
javier
previously approved these changes
Oct 19, 2026
javier
added a commit
that referenced
this pull request
Oct 19, 2026
…air (#581) **Draft: hold until the operator release that contains questdb/questdb-enterprise-operator#448.** Until then the published behaviour is still the old one. Operator change: a one-instance cluster no longer gets a PodDisruptionBudget by default, so a node drain or node upgrade restarts the database instead of hanging. - `known-limitations.md`: "Singleton drain is blocked by default" becomes "Draining a singleton's node restarts the database". - `configuration.md`: the default PDB applies to replicated clusters only; how to opt a singleton back in. - `operations/database.md`: the node maintenance section is rewritten for the new default. - Adds a note recommending node auto-repair for a node that is `NotReady` while its machine keeps running (the other half of questdb/questdb-enterprise-operator#64). Before merging: - `reference/api.md` is not touched; it is regenerated from the operator at release and will pick up the new field text then. - This overlaps #557, which edits the same opening of the node maintenance section in `operations/database.md`. Whichever merges second needs a rebase. - The auto-repair sentence says AKS repairs unhealthy nodes automatically and that EKS needs node auto repair enabled on the managed node group. Worth a check against current cloud docs. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com> Co-authored-by: javier ramírez <javier@questdb.io>
…ol-maintenance # Conflicts: # documentation/enterprise-kubernetes-operator/operations/database.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Documents a complete add-before-remove node-pool maintenance workflow for replicated QuestDB clusters:
It also documents the default hostname/zone placement behavior, scheduling overrides, same-zone capacity requirements, and safe stop/recovery points.
Why
The existing
instancesAPI already supports safe node-pool rotation through scale out → drain → scale in. A proposedspec.rotation.retireAPI in questdb/questdb-enterprise-operator#346 had no controller behavior and duplicated this workflow, so that PR was closed in favor of documenting the supported procedure.Verification
yarn buildgit diff --check