[tkkhq]

Tracking

• Tracks: https://konghq.atlassian.net/browse/VOL-1428

• Related: https://github.com/Kong/volcano-hosting/pull/3400

• Related: fix(transport): preserve retry delay on service unavailable responses volcano-sdk-python#428

• Related: fix(transport): preserve retry delay on service unavailable responses volcano-sdk-ruby#378

• Related: https://github.com/Kong/volcano-monitoring/pull/139

Why

• Callers need to distinguish a capacity refusal that happened before SQL dispatch from an ambiguous failure where replaying a write could duplicate its effects.

Summary

• describe the specific HTTP 503 capacity message and one-second retry hint in REST, JavaScript, Python and Ruby database guides
• require bounded application backoff and jitter; explain that a generic 503 alone does not establish safe write replay
• hold this documentation until the corresponding Hosting behavior and Python/Ruby SDK changes are released to production

Verification

• pnpm lint — no errors; three existing sidebar ternary warnings.
• pnpm lint:docs content/sdk/python
• pnpm lint:docs content/sdk/ruby
• pnpm lint:docs content/sdk/js
• pnpm lint:docs content/platform/databases
• pnpm build — site build, search index and server trace checks passed.