docs: document server.readinessHAMaxLag setting#414
Conversation
Documents the new arcadedb.server.readinessHAMaxLag config (default 100) introduced in ArcadeData/arcadedb#4846, which gates /api/v1/ready on committed Raft config membership and log catch-up, not just leader election, so a rolling restart cannot drop the write quorum. Also allowlists AKS in _typos.toml: the typos pre-commit hook was mis-correcting the Azure Kubernetes Service abbreviation to "ASK". Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QTCxkNzibBmXMHLEiK5Pkd
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request updates the documentation to describe a new High Availability readiness check behavior in ArcadeDB. When 'readinessRequiresHA' is enabled, a node must now also be part of the current Raft configuration and lag behind the commit index by no more than 'server.readinessHAMaxLag' entries (default 100) to be considered ready. Additionally, 'AKS' was added to the typos configuration file. There are no review comments, so I have no feedback to provide.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
1 participant
Documents the new arcadedb.server.readinessHAMaxLag config (default 100) introduced in ArcadeData/arcadedb#4846, which gates /api/v1/ready on committed Raft config membership and log catch-up, not just leader election, so a rolling restart cannot drop the write quorum.
Also allowlists AKS in _typos.toml: the typos pre-commit hook was mis-correcting the Azure Kubernetes Service abbreviation to "ASK".
Claude-Session: https://claude.ai/code/session_01QTCxkNzibBmXMHLEiK5Pkd