Kafka retry commit async on fail - why should I do so?
I use commit async with kafka (obviously without auto-commit).
Unfortunately, I came across the following exception:
error org.apache.kafka.clients.consumer.RetriableCommitFailedException: Offset commit failed with a retriable exception. You should retry committing the latest consumed offsets
After some investigation, I found out that even without committing offsets, the consumer keep on consuming messages from the topic.
After reading a little I saw that it is recommended to retry committing the offsets.
I don't understand why. The consumer is not threadsafe, therefore it is safe to assume that the retry already contains new offsets. And if so, wouldn't next commitAsync attempt suffice?
Regards,
Ido
apache-kafka kafka-consumer-api
add a comment |
I use commit async with kafka (obviously without auto-commit).
Unfortunately, I came across the following exception:
error org.apache.kafka.clients.consumer.RetriableCommitFailedException: Offset commit failed with a retriable exception. You should retry committing the latest consumed offsets
After some investigation, I found out that even without committing offsets, the consumer keep on consuming messages from the topic.
After reading a little I saw that it is recommended to retry committing the offsets.
I don't understand why. The consumer is not threadsafe, therefore it is safe to assume that the retry already contains new offsets. And if so, wouldn't next commitAsync attempt suffice?
Regards,
Ido
apache-kafka kafka-consumer-api
It'll keep consuming, but if the consumer restarts, then you'll re-process uncommitted offsets
– cricket_007
Nov 22 at 17:40
add a comment |
I use commit async with kafka (obviously without auto-commit).
Unfortunately, I came across the following exception:
error org.apache.kafka.clients.consumer.RetriableCommitFailedException: Offset commit failed with a retriable exception. You should retry committing the latest consumed offsets
After some investigation, I found out that even without committing offsets, the consumer keep on consuming messages from the topic.
After reading a little I saw that it is recommended to retry committing the offsets.
I don't understand why. The consumer is not threadsafe, therefore it is safe to assume that the retry already contains new offsets. And if so, wouldn't next commitAsync attempt suffice?
Regards,
Ido
apache-kafka kafka-consumer-api
I use commit async with kafka (obviously without auto-commit).
Unfortunately, I came across the following exception:
error org.apache.kafka.clients.consumer.RetriableCommitFailedException: Offset commit failed with a retriable exception. You should retry committing the latest consumed offsets
After some investigation, I found out that even without committing offsets, the consumer keep on consuming messages from the topic.
After reading a little I saw that it is recommended to retry committing the offsets.
I don't understand why. The consumer is not threadsafe, therefore it is safe to assume that the retry already contains new offsets. And if so, wouldn't next commitAsync attempt suffice?
Regards,
Ido
apache-kafka kafka-consumer-api
apache-kafka kafka-consumer-api
edited Nov 22 at 15:19
asked Nov 22 at 15:11
Ido Barash
1,55172951
1,55172951
It'll keep consuming, but if the consumer restarts, then you'll re-process uncommitted offsets
– cricket_007
Nov 22 at 17:40
add a comment |
It'll keep consuming, but if the consumer restarts, then you'll re-process uncommitted offsets
– cricket_007
Nov 22 at 17:40
It'll keep consuming, but if the consumer restarts, then you'll re-process uncommitted offsets
– cricket_007
Nov 22 at 17:40
It'll keep consuming, but if the consumer restarts, then you'll re-process uncommitted offsets
– cricket_007
Nov 22 at 17:40
add a comment |
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53433827%2fkafka-retry-commit-async-on-fail-why-should-i-do-so%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53433827%2fkafka-retry-commit-async-on-fail-why-should-i-do-so%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
It'll keep consuming, but if the consumer restarts, then you'll re-process uncommitted offsets
– cricket_007
Nov 22 at 17:40