Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add note about recreating ordered consumer #161

Merged
merged 2 commits into from Sep 29, 2022
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
6 changes: 5 additions & 1 deletion adr/ADR-17.md
Expand Up @@ -20,6 +20,8 @@ The subscription must track the last good stream and consumer sequences.
When a gap is observed, the subscription closes its current subscription,
releases its consumer and creates a new one starting at the proper stream sequence.

If hearbeats are missed, consumer might be gone (deleted, lost after reconnect, node restart, etc.), and it should be recreated from last known stream sequence.

You can optionally make the "state" available to the user.

### Subscription Limitations
Expand All @@ -40,8 +42,10 @@ Checks:
- durable_name: must not be provided
- deliver_subject: must not be provided
- ack policy: must not be provided or set to none. Set it to none if it is not provided.
- max_deliver: must be not be provided or set to 1. Set it to 1 if it is not provided.
- max_deliver: must not be provided or set to 1. Set it to 1 if it is not provided.
- flow_control: must not be provided or set true. Set it to true if it is not provided.
- mem_storage: must not be provided or set to true. Set to true if it is not provided.
- num_replicas: must not be provided. Set to 1.

Check and set these settings without an error:

Expand Down