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

Running in Distributed mode will cause large amounts of error messages about invalid task offsets #79

Open
forsberg opened this issue Nov 15, 2022 · 1 comment · May be fixed by #80
Open

Running in Distributed mode will cause large amounts of error messages about invalid task offsets #79

forsberg opened this issue Nov 15, 2022 · 1 comment · May be fixed by #80

Comments

@forsberg
Copy link
Contributor

When running in distributed mode, and after having tasks being reshuffled between kafka connect workers, a lot of these error messages will start showing up:

Ignoring invalid task provided offset
forsberg added a commit to forsberg/kafka-connect-scylladb that referenced this issue Nov 15, 2022
@forsberg
Correctly override close() and stop() as defined in SinkTask interface
91b64fd 
The implementation of close() will now remove TopicPartitions the task
no longer will have assigned. This will fix the problem where
the task logs that unassigned topic/partitions are reporting
commits at every commit.

stop() will now close the Scylla session, as intended in the API.

Fixes scylladb#79.
@forsberg forsberg linked a pull request Nov 15, 2022 that will close this issue
Open
@Bouncheck
Copy link
Collaborator

I've been unable to reproduce this issue using 1.0.2 version of the connector.
Do you remember if by any chance your configuration used any SMTs? @forsberg

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
2 participants
@forsberg @Bouncheck