docs(events,events-amqp): recovery backoff tuning, publisher shutdown, 1.2.0 currency#55
Merged
Merged
Conversation
…, 1.2.0 currency - events-amqp: precise recovery table semantics (symmetric jitter, cap overshoot, per-series maxRetries); new Tuning the reconnect backoff section with the verified full-jitter workaround + upstream links; 1.2.0 currency (failFastOnInitialSetupError row, onSetupFailed row + example, fail-fast notes in Connection Recovery) - events: Graceful Shutdown section — handler-drain semantics, await-before-stop publisher recipe, stopping-gate limitation (connectum#212), planned drainPublishTimeout (connectum#196) - en/api: TypeDoc regen (AmqpRecoveryOptions JSDoc + source-link shifts) Companion: Connectum-Framework/connectum#214 Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015Sp8jYmRXyvUmsErDuNJvt
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
1 participant
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.
Summary
Docs-site half of the 1.3.0 events cluster docs-first slice (companion to Connectum-Framework/connectum#214): accurate reconnect-delay semantics with the exact full-jitter workaround for
events-amqp, a Graceful Shutdown / publishers guide forevents, plus 1.2.0 currency fixes for theevents-amqppage.What changed
en/packages/events-amqp.md:AmqpRecoveryOptionstable: precisemaxDelay/jitter/maxRetriessemantics (symmetric jitter around the capped base; overshoot above the cap; per-series retry budget that resets on success).jitter: 1+ halvedinitialDelay/maxDelay→ delay uniform in[0, intended cap]), verified against amqplib 2.0.1, with a fragility caveat and upstream tracking links (recovery: allow a custom delay strategy (calculateDelay option) amqp-node/amqplib#855, recovery: separate retry budget for the initial connect amqp-node/amqplib#856).failFastOnInitialSetupErroroption row,onSetupFailedlifecycle row + config example line, fail-fast andmaxRetries-scope notes in Connection Recovery.en/packages/events.md:publish()promises are not tracked (drainTimeoutdoes not cover them); await-before-stop recipe for at-least-once producers; stopping-gate limitation for publishes from draining handlers (connectum#212); planned opt-indrainPublishTimeout(connectum#196).en/api/(generated): regenerated via TypeDoc from the companion branch —AmqpRecoveryOptionsJSDoc update plus source-link line shifts in the events-amqp package pages.Test plan
pnpm docs:buildpasses locally (dead-link check included, build 30s).gen-api-docs.shagainst the companion connectum branch.Related