-
Notifications
You must be signed in to change notification settings - Fork 146
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
Commit of offsets timed out - Many thread exceptions #221
Comments
From where are you running the connector? Is it in GCP or elsewhere? It could be an issue with the connection between wherever Kafka Connect is running and GCP. I see that the default retry settings in the connector are not set properly, so I will fix that. In the meantime, you could try setting the maxTotalTimeoutMs property to 60000. |
Actually, sorry, I was mistaken. The default is indeed 60s. Did you by chance change the value of maxTotalTimeoutMs? |
I didn't touch the default, I'm adding the full logs:
|
We found the DEADLINE_EXCEEDED in our systems in some cases, but at the moment we have not been able to reproduce them in a controlled environment. I subscribe because we are also after this case. |
Hi,
Suddenly we got exceptions with the connector.
I'm not sure but it seems that sending data to pubsub got exceptions for all parallel threads
I don't think it is Kafka issue because we have another tool that works fine but sending to kinesis.
Can someone help me to pinpoint the issue?
Thanks
and
The text was updated successfully, but these errors were encountered: