Spring Kafka producer requires restart











up vote
0
down vote

favorite












We have an issue where a Kafka partition outage (just 3 minutes) caused our producer to time out. We are producing with a 30 second timeout with 30 retries. After the partition outage ended, our Spring Kafka service producing to the topic required a service restart to start working. We are trying to understand a configuration missing or what issue did not allow our service threads to automatically resume the ability to publish to the topic without a service restart.



Below are details on how our producers look like. If you guys see something that you think we are doing wrong or can be done better, that will be helpful.



We are using kafka version 0.10



And the only custom config we are using is –



packEvent.producer.retries=30
packEvent.producer.acksConfig=1


Any thoughts on what was missing to not gracefully recover?










share|improve this question




















  • 1




    I suggest you turn on DEBUG logging for org.apache.kafka; it that doesn't help; post the logs someplace like pastebin/github gist. You should also edit your question to show exactly how you are using the peoducer.
    – Gary Russell
    Nov 8 at 21:32















up vote
0
down vote

favorite












We have an issue where a Kafka partition outage (just 3 minutes) caused our producer to time out. We are producing with a 30 second timeout with 30 retries. After the partition outage ended, our Spring Kafka service producing to the topic required a service restart to start working. We are trying to understand a configuration missing or what issue did not allow our service threads to automatically resume the ability to publish to the topic without a service restart.



Below are details on how our producers look like. If you guys see something that you think we are doing wrong or can be done better, that will be helpful.



We are using kafka version 0.10



And the only custom config we are using is –



packEvent.producer.retries=30
packEvent.producer.acksConfig=1


Any thoughts on what was missing to not gracefully recover?










share|improve this question




















  • 1




    I suggest you turn on DEBUG logging for org.apache.kafka; it that doesn't help; post the logs someplace like pastebin/github gist. You should also edit your question to show exactly how you are using the peoducer.
    – Gary Russell
    Nov 8 at 21:32













up vote
0
down vote

favorite









up vote
0
down vote

favorite











We have an issue where a Kafka partition outage (just 3 minutes) caused our producer to time out. We are producing with a 30 second timeout with 30 retries. After the partition outage ended, our Spring Kafka service producing to the topic required a service restart to start working. We are trying to understand a configuration missing or what issue did not allow our service threads to automatically resume the ability to publish to the topic without a service restart.



Below are details on how our producers look like. If you guys see something that you think we are doing wrong or can be done better, that will be helpful.



We are using kafka version 0.10



And the only custom config we are using is –



packEvent.producer.retries=30
packEvent.producer.acksConfig=1


Any thoughts on what was missing to not gracefully recover?










share|improve this question















We have an issue where a Kafka partition outage (just 3 minutes) caused our producer to time out. We are producing with a 30 second timeout with 30 retries. After the partition outage ended, our Spring Kafka service producing to the topic required a service restart to start working. We are trying to understand a configuration missing or what issue did not allow our service threads to automatically resume the ability to publish to the topic without a service restart.



Below are details on how our producers look like. If you guys see something that you think we are doing wrong or can be done better, that will be helpful.



We are using kafka version 0.10



And the only custom config we are using is –



packEvent.producer.retries=30
packEvent.producer.acksConfig=1


Any thoughts on what was missing to not gracefully recover?







apache-kafka spring-kafka






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 9 at 6:36









Giorgos Myrianthous

3,61121233




3,61121233










asked Nov 8 at 19:30









Kris

1




1








  • 1




    I suggest you turn on DEBUG logging for org.apache.kafka; it that doesn't help; post the logs someplace like pastebin/github gist. You should also edit your question to show exactly how you are using the peoducer.
    – Gary Russell
    Nov 8 at 21:32














  • 1




    I suggest you turn on DEBUG logging for org.apache.kafka; it that doesn't help; post the logs someplace like pastebin/github gist. You should also edit your question to show exactly how you are using the peoducer.
    – Gary Russell
    Nov 8 at 21:32








1




1




I suggest you turn on DEBUG logging for org.apache.kafka; it that doesn't help; post the logs someplace like pastebin/github gist. You should also edit your question to show exactly how you are using the peoducer.
– Gary Russell
Nov 8 at 21:32




I suggest you turn on DEBUG logging for org.apache.kafka; it that doesn't help; post the logs someplace like pastebin/github gist. You should also edit your question to show exactly how you are using the peoducer.
– Gary Russell
Nov 8 at 21:32

















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',
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
});


}
});














 

draft saved


draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53214861%2fspring-kafka-producer-requires-restart%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown






























active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes
















 

draft saved


draft discarded



















































 


draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53214861%2fspring-kafka-producer-requires-restart%23new-answer', 'question_page');
}
);

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







Popular posts from this blog

Schultheiß

Liste der Kulturdenkmale in Wilsdruff

Android Play Services Check