Skip to content

DOC-5208 cant to cannot (streaming learning) #55

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
May 9, 2025
Merged

DOC-5208 cant to cannot (streaming learning) #55

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion modules/subscriptions/pages/astream-subscriptions-exclusive.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -73,7 +73,7 @@ Exception in thread "main" java.lang.IllegalStateException: Cannot connect to pu
Caused by: org.apache.pulsar.client.api.PulsarClientException$ConsumerBusyException: {"errorMsg":"Exclusive consumer is already connected","reqId":2964994443801550457, "remote":"<service_url>", "local":"/192.168.0.95:55777"}
----

The second consumer can't subscribe to the topic because the subscription is *exclusive*. +
The second consumer cannot subscribe to the topic because the subscription is *exclusive*. +

In the example above, the consumer didn't declare a subscription type, so {pulsar-short} created an exclusive subscription by default. +
To explicitly define an exclusive subscription, add `.subscriptionType(SubscriptionType.Exclusive)` to the consumer.
Expand Down
2 changes: 1 addition & 1 deletion modules/subscriptions/pages/astream-subscriptions-keyshared.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -126,7 +126,7 @@ Caused by: org.apache.pulsar.client.api.PulsarClientException$ConsumerAssignExce
at com.datastax.pulsar.SimplePulsarConsumer.main(SimplePulsarConsumer.java:47)
----

The new consumer can't subscribe to the topic because you reserved the entire hash range for the first consumer.
The new consumer cannot subscribe to the topic because you reserved the entire hash range for the first consumer.

== Key_Shared subscription video

Expand Down
2 changes: 1 addition & 1 deletion modules/subscriptions/pages/astream-subscriptions-shared.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -70,7 +70,7 @@ The confirmation message and a cursor appear to indicate the consumer is ready.

. Open as many terminals as you'd like and run `SimplePulsarConsumer.java`. All the consumers subscribe to the topic and consume messages in a round-robin fashion.

If you run this test with xref:astream-subscriptions-exclusive.adoc[exclusive subscriptions], you can't attach more than once subscriber to the exclusive topic.
If you run this test with xref:astream-subscriptions-exclusive.adoc[exclusive subscriptions], you cannot attach more than once subscriber to the exclusive topic.
Since this test uses shared subscriptions, you can attach multiple consumers to the topic.

== Shared subscription video
Expand Down
2 changes: 1 addition & 1 deletion ...s/use-cases-architectures/pages/change-data-capture/questions-and-patterns.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -63,7 +63,7 @@ For more, see the https://docs.datastax.com/en/cdc-for-cassandra/docs/latest/ins
.Does the {cass-short} Source Connector use a dead-letter topic?
[%collapsible]
====
A dead letter topic is used when a message can't be delivered to a consumer. Maybe the message acknowledgment time expired (no consumer acknowledged receipt of the message), or a consumer negatively acknowledged the message, or a retry letter topic is in use and retries were exhausted.
A dead letter topic is used when a message cannot be delivered to a consumer. Maybe the message acknowledgment time expired (no consumer acknowledged receipt of the message), or a consumer negatively acknowledged the message, or a retry letter topic is in use and retries were exhausted.

The {cass-short} Source Connector creates a consumer to receive new event messages from the CDC agent, but does not configure a dead letter topic. It is assumed that parallel instances, broker compute, and function worker compute will be sized to handle the workload.
====
Expand Down