-
Notifications
You must be signed in to change notification settings - Fork 13.6k
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
KAFKA-3409: handle CommitFailedException in MirrorMaker #1115
Conversation
cc @becketqin @SinghAsDev @ijuma This is not significantly different from Ashish's patch, but I've added a log statement to give users more guidance if they see this occurring regularly. I think there's more we could be doing internally to mitigate this problem. For example, maybe it makes sense to set a default max.poll.records. Also we currently just block in the send loop after polling the records in receive(), but we probably should abort that loop immediately when the session timeout expires since we'll have no chance of committing offsets anyway. We could try to tackle some of this in this patch, but I'm thinking of opening a separate JIRA since a bigger change will be harder to get into 0.10. Thoughts? |
@hachikuji, filing a separate JIRA for the additional improvements sounds good to me. |
LGTM |
Looks good @hachikuji ! |
LGTM. |
Author: Jason Gustafson <jason@confluent.io> Reviewers: Ismael Juma, Ashish Singh, Guozhang Wang Closes #1115 from hachikuji/KAFKA-3409 (cherry picked from commit 20c3135) Signed-off-by: Guozhang Wang <wangguoz@gmail.com>
Merged to trunk and 0.10.0. |
No description provided.