Kafka retry on same topic
We would like to create a retry kafka mechanism for failures. I saw many introduced a way of have.multiple 'retry' topics. Was wondering why cant i simplify the flow by clone the message add into it a retry-counter field and just re-produce it on the same topic until reached X times and then exhausted.
What do I miss with that mechanism?
apache-kafka kafka-consumer-api kafka-producer-api
edited Nov 26 '18 at 6:48
Matthias J. Sax
29.7k45278
asked Nov 25 '18 at 21:24
raymanrayman
7,34233113208
add a comment |
We would like to create a retry kafka mechanism for failures. I saw many introduced a way of have.multiple 'retry' topics. Was wondering why cant i simplify the flow by clone the message add into it a retry-counter field and just re-produce it on the same topic until reached X times and then exhausted.
What do I miss with that mechanism?
apache-kafka kafka-consumer-api kafka-producer-api
edited Nov 26 '18 at 6:48
Matthias J. Sax
29.7k45278
asked Nov 25 '18 at 21:24
raymanrayman
7,34233113208
add a comment |
We would like to create a retry kafka mechanism for failures. I saw many introduced a way of have.multiple 'retry' topics. Was wondering why cant i simplify the flow by clone the message add into it a retry-counter field and just re-produce it on the same topic until reached X times and then exhausted.
What do I miss with that mechanism?
apache-kafka kafka-consumer-api kafka-producer-api
edited Nov 26 '18 at 6:48
Matthias J. Sax
29.7k45278
asked Nov 25 '18 at 21:24
raymanrayman
7,34233113208
We would like to create a retry kafka mechanism for failures. I saw many introduced a way of have.multiple 'retry' topics. Was wondering why cant i simplify the flow by clone the message add into it a retry-counter field and just re-produce it on the same topic until reached X times and then exhausted.
What do I miss with that mechanism?
apache-kafka kafka-consumer-api kafka-producer-api
apache-kafka kafka-consumer-api kafka-producer-api
edited Nov 26 '18 at 6:48
Matthias J. Sax
29.7k45278
asked Nov 25 '18 at 21:24
raymanrayman
7,34233113208
edited Nov 26 '18 at 6:48
Matthias J. Sax
29.7k45278
asked Nov 25 '18 at 21:24
raymanrayman
7,34233113208
edited Nov 26 '18 at 6:48
Matthias J. Sax
29.7k45278
edited Nov 26 '18 at 6:48
Matthias J. Sax
29.7k45278
edited Nov 26 '18 at 6:48
Matthias J. Sax
29.7k45278
29.7k45278
asked Nov 25 '18 at 21:24
raymanrayman
7,34233113208
asked Nov 25 '18 at 21:24
raymanrayman
7,34233113208
asked Nov 25 '18 at 21:24
raymanrayman
7,34233113208
7,34233113208
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Not Sure if I understand the question correctly. Nevertheless, I would suggest that you have some Kafka 'retry' strategies.
- Messages in 'retry' topics are already sorted in ‘retry_timestamp’
order - Because postponing message processing in case of failure is not a trivial process
- If you would like to postpone processing of
some messages, you can republish them to separate topics, one for
each with some delay value - The failed messages processing can be
achieved by cloning the message and later republishing it to one of
the retry topics - Consumers of retry topics could block the thread
(unless it is time to process the message)
answered Nov 25 '18 at 22:12
UnPUnP
7111
thanks for your reply. how Messages in 'retry' topics are already sorted in ‘retry_timestamp’ order ?? i mean if i take them in batch there is a chanse that ill miss the retry buffer time coz the same message wont be on that batch
– rayman
Nov 26 '18 at 9:07
add a comment |
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%2f53472143%2fkafka-retry-on-same-topic%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Not Sure if I understand the question correctly. Nevertheless, I would suggest that you have some Kafka 'retry' strategies.
- Messages in 'retry' topics are already sorted in ‘retry_timestamp’
order - Because postponing message processing in case of failure is not a trivial process
- If you would like to postpone processing of
some messages, you can republish them to separate topics, one for
each with some delay value - The failed messages processing can be
achieved by cloning the message and later republishing it to one of
the retry topics - Consumers of retry topics could block the thread
(unless it is time to process the message)
answered Nov 25 '18 at 22:12
UnPUnP
7111
thanks for your reply. how Messages in 'retry' topics are already sorted in ‘retry_timestamp’ order ?? i mean if i take them in batch there is a chanse that ill miss the retry buffer time coz the same message wont be on that batch
– rayman
Nov 26 '18 at 9:07
add a comment |
Not Sure if I understand the question correctly. Nevertheless, I would suggest that you have some Kafka 'retry' strategies.
- Messages in 'retry' topics are already sorted in ‘retry_timestamp’
order - Because postponing message processing in case of failure is not a trivial process
- If you would like to postpone processing of
some messages, you can republish them to separate topics, one for
each with some delay value - The failed messages processing can be
achieved by cloning the message and later republishing it to one of
the retry topics - Consumers of retry topics could block the thread
(unless it is time to process the message)
answered Nov 25 '18 at 22:12
UnPUnP
7111
thanks for your reply. how Messages in 'retry' topics are already sorted in ‘retry_timestamp’ order ?? i mean if i take them in batch there is a chanse that ill miss the retry buffer time coz the same message wont be on that batch
– rayman
Nov 26 '18 at 9:07
add a comment |
Not Sure if I understand the question correctly. Nevertheless, I would suggest that you have some Kafka 'retry' strategies.
- Messages in 'retry' topics are already sorted in ‘retry_timestamp’
order - Because postponing message processing in case of failure is not a trivial process
- If you would like to postpone processing of
some messages, you can republish them to separate topics, one for
each with some delay value - The failed messages processing can be
achieved by cloning the message and later republishing it to one of
the retry topics - Consumers of retry topics could block the thread
(unless it is time to process the message)
answered Nov 25 '18 at 22:12
UnPUnP
7111
Not Sure if I understand the question correctly. Nevertheless, I would suggest that you have some Kafka 'retry' strategies.
- Messages in 'retry' topics are already sorted in ‘retry_timestamp’
order - Because postponing message processing in case of failure is not a trivial process
- If you would like to postpone processing of
some messages, you can republish them to separate topics, one for
each with some delay value - The failed messages processing can be
achieved by cloning the message and later republishing it to one of
the retry topics - Consumers of retry topics could block the thread
(unless it is time to process the message)
answered Nov 25 '18 at 22:12
UnPUnP
7111
answered Nov 25 '18 at 22:12
UnPUnP
7111
answered Nov 25 '18 at 22:12
UnPUnP
7111
answered Nov 25 '18 at 22:12
UnPUnP
7111
7111
thanks for your reply. how Messages in 'retry' topics are already sorted in ‘retry_timestamp’ order ?? i mean if i take them in batch there is a chanse that ill miss the retry buffer time coz the same message wont be on that batch
– rayman
Nov 26 '18 at 9:07
add a comment |
thanks for your reply. how Messages in 'retry' topics are already sorted in ‘retry_timestamp’ order ?? i mean if i take them in batch there is a chanse that ill miss the retry buffer time coz the same message wont be on that batch
– rayman
Nov 26 '18 at 9:07
thanks for your reply. how Messages in 'retry' topics are already sorted in ‘retry_timestamp’ order ?? i mean if i take them in batch there is a chanse that ill miss the retry buffer time coz the same message wont be on that batch
– rayman
Nov 26 '18 at 9:07
thanks for your reply. how Messages in 'retry' topics are already sorted in ‘retry_timestamp’ order ?? i mean if i take them in batch there is a chanse that ill miss the retry buffer time coz the same message wont be on that batch
– rayman
Nov 26 '18 at 9:07
add a comment |
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.
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%2f53472143%2fkafka-retry-on-same-topic%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
