[ 
https://issues.apache.org/jira/browse/FLINK-17949?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17126348#comment-17126348
 ] 

Yuan Mei edited comment on FLINK-17949 at 6/5/20, 3:46 AM:
-----------------------------------------------------------

Thanks, [~rmetzger] , I got a bit more msg this time:

It does sound like a metadata fetching problem.
{code:java}
13:34:40,706 [kafka-producer-network-thread | producer-7] WARN 
org.apache.kafka.clients.producer.internals.Sender [] - [Producer 
clientId=producer-7] Got error produce response with correlation id 9 on 
topic-partition test_serde_IngestionTime-0, retrying (2147483646 attempts 
left). Error: UNKNOWN_TOPIC_OR_PARTITION
13:34:40,706 [kafka-producer-network-thread | producer-7] WARN 
org.apache.kafka.clients.producer.internals.Sender [] - [Producer 
clientId=producer-7] Received unknown topic or partition error in produce 
request on partition test_serde_IngestionTime-0. The topic-partition may not 
exist or the user may not have Describe access to it
13:34:40,854 [kafka-producer-network-thread | producer-7] WARN 
org.apache.kafka.clients.NetworkClient [] - [Producer clientId=producer-7] 
Error while fetching metadata with correlation id 12 : 
{test_serde_IngestionTime=LEADER_NOT_AVAILABLE}{code}
 

I was wondering whether similar cases happen before while using Kafka, and how 
this situation could be avoided?

[~aljoscha]

 


was (Author: ym):
Thanks, Robert, I got a bit more msg this time:

 
{code:java}
13:34:40,706 [kafka-producer-network-thread | producer-7] WARN 
org.apache.kafka.clients.producer.internals.Sender [] - [Producer 
clientId=producer-7] Got error produce response with correlation id 9 on 
topic-partition test_serde_IngestionTime-0, retrying (2147483646 attempts 
left). Error: UNKNOWN_TOPIC_OR_PARTITION
13:34:40,706 [kafka-producer-network-thread | producer-7] WARN 
org.apache.kafka.clients.producer.internals.Sender [] - [Producer 
clientId=producer-7] Received unknown topic or partition error in produce 
request on partition test_serde_IngestionTime-0. The topic-partition may not 
exist or the user may not have Describe access to it
13:34:40,854 [kafka-producer-network-thread | producer-7] WARN 
org.apache.kafka.clients.NetworkClient [] - [Producer clientId=producer-7] 
Error while fetching metadata with correlation id 12 : 
{test_serde_IngestionTime=LEADER_NOT_AVAILABLE}{code}
 

 

> KafkaShuffleITCase.testSerDeIngestionTime:156->testRecordSerDe:388 
> expected:<310> but was:<0>
> ---------------------------------------------------------------------------------------------
>
>                 Key: FLINK-17949
>                 URL: https://issues.apache.org/jira/browse/FLINK-17949
>             Project: Flink
>          Issue Type: Bug
>          Components: Connectors / Kafka, Tests
>    Affects Versions: 1.11.0, 1.12.0
>            Reporter: Robert Metzger
>            Priority: Critical
>              Labels: test-stability
>         Attachments: logs-ci-kafkagelly-1590500380.zip, 
> logs-ci-kafkagelly-1590524911.zip
>
>
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=2209&view=logs&j=c5f0071e-1851-543e-9a45-9ac140befc32&t=684b1416-4c17-504e-d5ab-97ee44e08a20
> {code}
> 2020-05-26T13:35:19.4022562Z [ERROR] 
> testSerDeIngestionTime(org.apache.flink.streaming.connectors.kafka.shuffle.KafkaShuffleITCase)
>   Time elapsed: 5.786 s  <<< FAILURE!
> 2020-05-26T13:35:19.4023185Z java.lang.AssertionError: expected:<310> but 
> was:<0>
> 2020-05-26T13:35:19.4023498Z  at org.junit.Assert.fail(Assert.java:88)
> 2020-05-26T13:35:19.4023825Z  at 
> org.junit.Assert.failNotEquals(Assert.java:834)
> 2020-05-26T13:35:19.4024461Z  at 
> org.junit.Assert.assertEquals(Assert.java:645)
> 2020-05-26T13:35:19.4024900Z  at 
> org.junit.Assert.assertEquals(Assert.java:631)
> 2020-05-26T13:35:19.4028546Z  at 
> org.apache.flink.streaming.connectors.kafka.shuffle.KafkaShuffleITCase.testRecordSerDe(KafkaShuffleITCase.java:388)
> 2020-05-26T13:35:19.4029629Z  at 
> org.apache.flink.streaming.connectors.kafka.shuffle.KafkaShuffleITCase.testSerDeIngestionTime(KafkaShuffleITCase.java:156)
> 2020-05-26T13:35:19.4030253Z  at 
> sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 2020-05-26T13:35:19.4030673Z  at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> 2020-05-26T13:35:19.4031332Z  at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 2020-05-26T13:35:19.4031763Z  at 
> java.lang.reflect.Method.invoke(Method.java:498)
> 2020-05-26T13:35:19.4032155Z  at 
> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> 2020-05-26T13:35:19.4032630Z  at 
> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> 2020-05-26T13:35:19.4033188Z  at 
> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> 2020-05-26T13:35:19.4033638Z  at 
> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
> 2020-05-26T13:35:19.4034103Z  at 
> org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> 2020-05-26T13:35:19.4034593Z  at 
> org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:298)
> 2020-05-26T13:35:19.4035118Z  at 
> org.junit.internal.runners.statements.FailOnTimeout$CallableStatement.call(FailOnTimeout.java:292)
> 2020-05-26T13:35:19.4035570Z  at 
> java.util.concurrent.FutureTask.run(FutureTask.java:266)
> 2020-05-26T13:35:19.4035888Z  at java.lang.Thread.run(Thread.java:748)
> {code}



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

Reply via email to