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

DBZ-6461 Debezium Server cannot recover from Google Pub/Sub errors #23

Merged
merged 2 commits into from May 16, 2023

Conversation

mfvitale
Copy link
Member

@mfvitale mfvitale commented May 15, 2023

Add properties
debezium.sink.pubsub.wait.message.computation.timeout.ms and debezium.sink.pubsublite.wait.message.computation.timeout.ms
to configure the wait time on message processing by Google PubSub. In this wait the connector can fail and be restarted.

Doc PR debezium/debezium#4544

…n.timeout.ms` and `debezium.sink.pubsublite.wait.message.computation.timeout.ms` to configure the wait time on message processing by Google PubSub
@@ -123,6 +125,9 @@ public interface PublisherBuilder {
@ConfigProperty(name = PROP_PREFIX + "retry.rpc.timeout.multiplier", defaultValue = "2.0")
Double rpcTimeoutMultiplier;

@ConfigProperty(name = PROP_PREFIX + "wait.message.computation.timeout.ms", defaultValue = "5000")
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mfvitale We are going from unlimited. It is really hard to know what is the usual time till the mesage batch is written.
Is not 5 secs value a bit too aggressive? I'd prefer to err on the safe side at least in the beginning and choose 30 or 60 secs.
Also why computation? Would not delivery be better to represent the value use?

@jpechane jpechane merged commit e6786b4 into debezium:main May 16, 2023
2 checks passed
@jpechane
Copy link
Contributor

@mfvitale Applied, thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants