[ 
https://issues.apache.org/jira/browse/KAFKA-9722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Artem Loginov updated KAFKA-9722:
---------------------------------
    Description: 
Hello,

I have an issue with kafka in my app. It suddenly stops consuming new messages 
and I don't know what to do.
 I've posted an issue on spring-cloud-kafka github but they kindly redirected 
me to the kafka project saying this is nothing to do with spring.
 Here are the issue 
[https://github.com/spring-cloud/spring-cloud-stream/issues/1928#event-3127969583]
 Please help since my app could only work for couple hours in production env 
and then it just stop doing the work before I restart it. I can provide any 
additional configuration you need.

Thank you for help.

UPD (_16 Mar 2020)_:

According to [~bchen225242] comment here is the summarized error description.
 After some time I receive a lot of: 
{code:java}
Offset commit failed on partition topic.name-57 at offset 31282126: The request 
timed out.
{code}
{{and a couple of }}
{code:java}
org.apache.kafka.common.errors.NotLeaderForPartitionException: This server is 
not the leader for that topic-partition{code}
after which my app stop consuming from kafka topics. But continue to send 
messages.

 Regarding the config, I basically use 
{color:#172b4d}{color:#6a8759}spring-cloud-starter-stream-kafka defaults with 
this additional properties{color}{color}
{code:java}
spring.cloud.stream.bindings.inputEvent.destination=topic-2.name
spring.cloud.stream.bindings.inputEvent.group=${spring.application.name}
spring.cloud.stream.bindings.outputEvent.destination=topic-2.name

spring.cloud.stream.bindings.inputTopicName.destination=topic.name
spring.cloud.stream.bindings.inputTopicName.group=${spring.application.name}
spring.cloud.stream.bindings.outputTopicName.destination=topic.name

spring.kafka.consumer.group-id=${spring.application.name}
spring.kafka.consumer.auto-offset-reset=earliest
spring.kafka.bootstrap-servers=kafka-bootstrap-servver:9092

spring.cloud.stream.kafka.binder.producer-properties.key.serializer=org.apache.kafka.common.serialization.StringSerializer
{code}
{color:#6a8759}I am honestly not sure if this is the config you are looking 
for. Let me know if you need anything extra and I will do my best to provide 
required information.{color}

  was:
Hello,

I have an issue with kafka in my app. It suddenly stops consuming new messages 
and I don't know what to do.
 I've posted an issue on spring-cloud-kafka github but they kindly redirected 
me to the kafka project saying this is nothing to do with spring.
 Here are the issue 
[https://github.com/spring-cloud/spring-cloud-stream/issues/1928#event-3127969583]
 Please help since my app could only work for couple hours in production env 
and then it just stop doing the work before I restart it. I can provide any 
additional configuration you need.

Thank you for help.

UPD (_16 Mar 2020)_:

According to [~bchen225242] comment here is the summarized error description.
 After some time I receive a lot of: 
{code:java}
Offset commit failed on partition topic.name-57 at offset 31282126: The request 
timed out.
{code}
{{and a couple of }}
{code:java}
org.apache.kafka.common.errors.NotLeaderForPartitionException: This server is 
not the leader for that topic-partition{code}
after which my app stop consuming from kafka topics. But continue to send 
messages.

 Regarding the config, I basically use 
{color:#6a8759}spring-cloud-starter-stream-kafka defaults with this additional 
properties
{color}
{code:java}
spring.cloud.stream.bindings.inputEvent.destination=topic-2.name
spring.cloud.stream.bindings.inputEvent.group=${spring.application.name}
spring.cloud.stream.bindings.outputEvent.destination=topic-2.name

spring.cloud.stream.bindings.inputTopicName.destination=topic.name
spring.cloud.stream.bindings.inputTopicName.group=${spring.application.name}
spring.cloud.stream.bindings.outputTopicName.destination=topic.name

spring.kafka.consumer.group-id=${spring.application.name}
spring.kafka.consumer.auto-offset-reset=earliest
spring.kafka.bootstrap-servers=kafka-bootstrap-servver:9092

spring.cloud.stream.kafka.binder.producer-properties.key.serializer=org.apache.kafka.common.serialization.StringSerializer
{code}
{color:#6a8759}I am honestly not sure if this is the config you are looking 
for. Let me know if you need anything extra and I will do my best to provide 
required information.
{color}


> Kafka stops consuming messages after error
> ------------------------------------------
>
>                 Key: KAFKA-9722
>                 URL: https://issues.apache.org/jira/browse/KAFKA-9722
>             Project: Kafka
>          Issue Type: Bug
>    Affects Versions: 2.3.1
>            Reporter: Artem Loginov
>            Priority: Major
>
> Hello,
> I have an issue with kafka in my app. It suddenly stops consuming new 
> messages and I don't know what to do.
>  I've posted an issue on spring-cloud-kafka github but they kindly redirected 
> me to the kafka project saying this is nothing to do with spring.
>  Here are the issue 
> [https://github.com/spring-cloud/spring-cloud-stream/issues/1928#event-3127969583]
>  Please help since my app could only work for couple hours in production env 
> and then it just stop doing the work before I restart it. I can provide any 
> additional configuration you need.
> Thank you for help.
> UPD (_16 Mar 2020)_:
> According to [~bchen225242] comment here is the summarized error description.
>  After some time I receive a lot of: 
> {code:java}
> Offset commit failed on partition topic.name-57 at offset 31282126: The 
> request timed out.
> {code}
> {{and a couple of }}
> {code:java}
> org.apache.kafka.common.errors.NotLeaderForPartitionException: This server is 
> not the leader for that topic-partition{code}
> after which my app stop consuming from kafka topics. But continue to send 
> messages.
>  Regarding the config, I basically use 
> {color:#172b4d}{color:#6a8759}spring-cloud-starter-stream-kafka defaults with 
> this additional properties{color}{color}
> {code:java}
> spring.cloud.stream.bindings.inputEvent.destination=topic-2.name
> spring.cloud.stream.bindings.inputEvent.group=${spring.application.name}
> spring.cloud.stream.bindings.outputEvent.destination=topic-2.name
> spring.cloud.stream.bindings.inputTopicName.destination=topic.name
> spring.cloud.stream.bindings.inputTopicName.group=${spring.application.name}
> spring.cloud.stream.bindings.outputTopicName.destination=topic.name
> spring.kafka.consumer.group-id=${spring.application.name}
> spring.kafka.consumer.auto-offset-reset=earliest
> spring.kafka.bootstrap-servers=kafka-bootstrap-servver:9092
> spring.cloud.stream.kafka.binder.producer-properties.key.serializer=org.apache.kafka.common.serialization.StringSerializer
> {code}
> {color:#6a8759}I am honestly not sure if this is the config you are looking 
> for. Let me know if you need anything extra and I will do my best to provide 
> required information.{color}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to