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.

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

Jump to bottom

ZeebeSourceTaskFetcher changes requestTimeout for Zeebe based on its internal backoff algorithm #223

Open
aanodin opened this issue Jun 17, 2024 · 1 comment · May be fixed by #224
Open

ZeebeSourceTaskFetcher changes requestTimeout for Zeebe based on its internal backoff algorithm #223

aanodin opened this issue Jun 17, 2024 · 1 comment · May be fixed by #224

Comments

@aanodin
Copy link
Contributor

aanodin commented Jun 17, 2024

The setting zeebe.client.requestTimeout must be used as a constant for ActivateJobs requests, but it internally changed by ZeebeSourceTaskFetcher based on backoff algorithm.
This causes many unprocessable requests to Zeebe with very small timeouts such as -1 ms, 100 ms, 200 ms, etc.

Log:
[2024-06-17 06:15:29,637] TRACE Sending activate jobs command for maximal 20 jobs of type sendZeebeMessage with request timeout PT-0.001S (io.zeebe.kafka.connect.source.ZeebeSourceTaskFetcher)
@aanodin aanodin linked a pull request Jun 17, 2024 that will close this issue
Open
@aanodin
Copy link
Contributor Author

aanodin commented Jun 17, 2024

@berndruecker please take a look at fix #224
could you please merge it and build a new image of kafka-connect-zeebe?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
1 participant
@aanodin