-
Notifications
You must be signed in to change notification settings - Fork 15
Add support for single active consumer and super streams #46
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
Comments
acogoluegnes
added a commit
that referenced
this issue
Dec 1, 2021
Requires to add Consumer#storedOffset() to let the user make sure the stored offset request made it to the broker before closing the consumer. References #46, rabbitmq/rabbitmq-server#3753
May require to add |
acogoluegnes
added a commit
that referenced
this issue
Dec 2, 2021
Mainly queryOffset returning QueryOffsetResponse instead of just a long. References #46, rabbitmq/rabbitmq-server#3753
acogoluegnes
added a commit
that referenced
this issue
Dec 2, 2021
Requires to add Consumer#storedOffset() to let the user make sure the stored offset request made it to the broker before closing the consumer. References #46, rabbitmq/rabbitmq-server#3753
acogoluegnes
added a commit
that referenced
this issue
Dec 2, 2021
Mainly queryOffset returning QueryOffsetResponse instead of just a long. References #46, rabbitmq/rabbitmq-server#3753
acogoluegnes
added a commit
that referenced
this issue
Dec 2, 2021
Requires to add Consumer#storedOffset() to let the user make sure the stored offset request made it to the broker before closing the consumer. References #46, rabbitmq/rabbitmq-server#3753
acogoluegnes
added a commit
that referenced
this issue
Dec 3, 2021
acogoluegnes
added a commit
that referenced
this issue
Dec 6, 2021
Using server-side offset tracking. References #46, rabbitmq/rabbitmq-server#3753
acogoluegnes
added a commit
that referenced
this issue
Dec 6, 2021
acogoluegnes
added a commit
that referenced
this issue
Dec 9, 2021
acogoluegnes
added a commit
that referenced
this issue
Dec 10, 2021
Mainly queryOffset returning QueryOffsetResponse instead of just a long. References #46, rabbitmq/rabbitmq-server#3753
acogoluegnes
added a commit
that referenced
this issue
Dec 10, 2021
Requires to add Consumer#storedOffset() to let the user make sure the stored offset request made it to the broker before closing the consumer. References #46, rabbitmq/rabbitmq-server#3753
acogoluegnes
added a commit
that referenced
this issue
Dec 10, 2021
acogoluegnes
added a commit
that referenced
this issue
Dec 10, 2021
Using server-side offset tracking. References #46, rabbitmq/rabbitmq-server#3753
acogoluegnes
added a commit
that referenced
this issue
Dec 10, 2021
acogoluegnes
added a commit
that referenced
this issue
Dec 10, 2021
acogoluegnes
added a commit
that referenced
this issue
Dec 15, 2021
The (de)activation protocol changed a bit internally. New consumers assume they are passive by default, until they are activated (no passive update notification if the consumer was not active previously). References #46, rabbitmq/rabbitmq-server#3753
acogoluegnes
added a commit
that referenced
this issue
Dec 16, 2021
Mainly queryOffset returning QueryOffsetResponse instead of just a long. References #46, rabbitmq/rabbitmq-server#3753
acogoluegnes
added a commit
that referenced
this issue
Dec 16, 2021
Requires to add Consumer#storedOffset() to let the user make sure the stored offset request made it to the broker before closing the consumer. References #46, rabbitmq/rabbitmq-server#3753
acogoluegnes
added a commit
that referenced
this issue
Dec 16, 2021
acogoluegnes
added a commit
that referenced
this issue
Dec 16, 2021
Using server-side offset tracking. References #46, rabbitmq/rabbitmq-server#3753
acogoluegnes
added a commit
that referenced
this issue
Dec 16, 2021
acogoluegnes
added a commit
that referenced
this issue
Dec 16, 2021
acogoluegnes
added a commit
that referenced
this issue
Dec 16, 2021
The (de)activation protocol changed a bit internally. New consumers assume they are passive by default, until they are activated (no passive update notification if the consumer was not active previously). References #46, rabbitmq/rabbitmq-server#3753
acogoluegnes
added a commit
that referenced
this issue
Dec 16, 2021
Mainly queryOffset returning QueryOffsetResponse instead of just a long. References #46, rabbitmq/rabbitmq-server#3753
acogoluegnes
added a commit
that referenced
this issue
Dec 16, 2021
Requires to add Consumer#storedOffset() to let the user make sure the stored offset request made it to the broker before closing the consumer. References #46, rabbitmq/rabbitmq-server#3753
acogoluegnes
added a commit
that referenced
this issue
Dec 16, 2021
acogoluegnes
added a commit
that referenced
this issue
Dec 16, 2021
Using server-side offset tracking. References #46, rabbitmq/rabbitmq-server#3753
acogoluegnes
added a commit
that referenced
this issue
Jul 13, 2022
Setting the SAC status to false is safe when the connection is lost, even if no notification came. This makes sure the consumer instance state is consistent, as a new SAC consumer is always inactive when it first registers. References #46
acogoluegnes
added a commit
that referenced
this issue
Aug 10, 2022
Mainly queryOffset returning QueryOffsetResponse instead of just a long. References #46, rabbitmq/rabbitmq-server#3753 Conflicts: src/main/java/com/rabbitmq/stream/impl/OffsetTrackingCoordinator.java
acogoluegnes
added a commit
that referenced
this issue
Aug 10, 2022
Requires to add Consumer#storedOffset() to let the user make sure the stored offset request made it to the broker before closing the consumer. References #46, rabbitmq/rabbitmq-server#3753 Conflicts: src/main/java/com/rabbitmq/stream/impl/OffsetTrackingCoordinator.java
acogoluegnes
added a commit
that referenced
this issue
Aug 10, 2022
acogoluegnes
added a commit
that referenced
this issue
Aug 10, 2022
Using server-side offset tracking. References #46, rabbitmq/rabbitmq-server#3753
acogoluegnes
added a commit
that referenced
this issue
Aug 10, 2022
acogoluegnes
added a commit
that referenced
this issue
Aug 10, 2022
acogoluegnes
added a commit
that referenced
this issue
Aug 10, 2022
The (de)activation protocol changed a bit internally. New consumers assume they are passive by default, until they are activated (no passive update notification if the consumer was not active previously). References #46, rabbitmq/rabbitmq-server#3753
acogoluegnes
added a commit
that referenced
this issue
Aug 10, 2022
The stream SAC coordinator monitors connection processes and should send consumer update accordingly when connections die. References #46, rabbitmq/rabbitmq-server#3753
acogoluegnes
added a commit
that referenced
this issue
Aug 10, 2022
acogoluegnes
added a commit
that referenced
this issue
Aug 10, 2022
acogoluegnes
added a commit
that referenced
this issue
Aug 10, 2022
Otherwise the expected response code may not be received because there's no enough concurrency. This way an error path is exercised on the broker side. References #46, rabbitmq/rabbitmq-server#3753
acogoluegnes
added a commit
that referenced
this issue
Aug 10, 2022
acogoluegnes
added a commit
that referenced
this issue
Aug 10, 2022
acogoluegnes
added a commit
that referenced
this issue
Aug 10, 2022
Instead of state enum. This is a boolean, and as the consumer is notified only of a state change, it does not have to know about the previous state. References #46 Conflicts: src/main/java/com/rabbitmq/stream/impl/OffsetTrackingCoordinator.java src/main/java/com/rabbitmq/stream/impl/StreamConsumer.java
acogoluegnes
added a commit
that referenced
this issue
Aug 10, 2022
acogoluegnes
added a commit
that referenced
this issue
Aug 10, 2022
Thrown when no stored offset is found. Better than checking response code. References #46 Conflicts: src/main/java/com/rabbitmq/stream/impl/OffsetTrackingCoordinator.java
acogoluegnes
added a commit
that referenced
this issue
Aug 10, 2022
acogoluegnes
added a commit
that referenced
this issue
Aug 10, 2022
To disable server-side offset tracking. Useful when SAC is enabled and external storage is used for offset tracking. References #46
acogoluegnes
added a commit
that referenced
this issue
Aug 10, 2022
acogoluegnes
added a commit
that referenced
this issue
Aug 10, 2022
References #46 Conflicts: pom.xml
acogoluegnes
added a commit
that referenced
this issue
Aug 10, 2022
acogoluegnes
added a commit
that referenced
this issue
Aug 10, 2022
Setting the SAC status to false is safe when the connection is lost, even if no notification came. This makes sure the consumer instance state is consistent, as a new SAC consumer is always inactive when it first registers. References #46
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
References rabbitmq/rabbitmq-server#3753.
The text was updated successfully, but these errors were encountered: