[
https://issues.apache.org/jira/browse/FLINK-31446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17707191#comment-17707191
]
Matthias Pohl commented on FLINK-31446:
---------------------------------------
Here is one where it fails due to a timeout:
https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=47750&view=logs&j=8eee98ee-a482-5f7c-2c51-b3456453e704&t=da58e781-88fe-508b-b74c-018210e533cc&l=36635
{code}
Caused by: org.apache.flink.runtime.JobException: Recovery is suppressed by
FixedDelayRestartBackoffTimeStrategy(maxNumberRestartAttempts=1,
backoffTimeMS=0)
at
org.apache.flink.runtime.executiongraph.failover.flip1.ExecutionFailureHandler.handleFailure(ExecutionFailureHandler.java:139)
at
org.apache.flink.runtime.executiongraph.failover.flip1.ExecutionFailureHandler.getFailureHandlingResult(ExecutionFailureHandler.java:83)
at
org.apache.flink.runtime.scheduler.DefaultScheduler.recordTaskFailure(DefaultScheduler.java:258)
at
org.apache.flink.runtime.scheduler.DefaultScheduler.handleTaskFailure(DefaultScheduler.java:249)
at
org.apache.flink.runtime.scheduler.DefaultScheduler.onTaskFailed(DefaultScheduler.java:242)
at
org.apache.flink.runtime.scheduler.SchedulerBase.onTaskExecutionStateUpdate(SchedulerBase.java:748)
at
org.apache.flink.runtime.scheduler.SchedulerBase.updateTaskExecutionState(SchedulerBase.java:725)
at
org.apache.flink.runtime.scheduler.SchedulerNG.updateTaskExecutionState(SchedulerNG.java:80)
at
org.apache.flink.runtime.jobmaster.JobMaster.updateTaskExecutionState(JobMaster.java:479)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
[...]
... 4 more
Caused by: org.apache.kafka.common.errors.TimeoutException:
org.apache.kafka.common.errors.TimeoutException: Timeout expired after 60000ms
while awaiting InitProducerId
Caused by: org.apache.kafka.common.errors.TimeoutException: Timeout expired
after 60000ms while awaiting InitProducerId
{code}
I'm adding it here because we're seeing the createTopic and timeout issues
constantly in different tests. We have to stabilize the Kafka tests in this
regards, I guess. I moved this issue under the umbrella ticket FLINK-31145
> KafkaSinkITCase$IntegrationTests.testMetrics failed because topic XXX already
> exists
> ------------------------------------------------------------------------------------
>
> Key: FLINK-31446
> URL: https://issues.apache.org/jira/browse/FLINK-31446
> Project: Flink
> Issue Type: Sub-task
> Components: Connectors / Kafka
> Reporter: Martijn Visser
> Priority: Major
> Labels: test-stability
>
> {code:java}
> Mar 14 02:07:46 at
> org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$8(NodeTestTask.java:141)
> Mar 14 02:07:46 at
> org.junit.platform.engine.support.hierarchical.Node.around(Node.java:137)
> Mar 14 02:07:46 at
> org.junit.platform.engine.support.hierarchical.NodeTestTask.lambda$executeRecursively$9(NodeTestTask.java:139)
> Mar 14 02:07:46 at
> org.junit.platform.engine.support.hierarchical.ThrowableCollector.execute(ThrowableCollector.java:73)
> Mar 14 02:07:46 at
> org.junit.platform.engine.support.hierarchical.NodeTestTask.executeRecursively(NodeTestTask.java:138)
> Mar 14 02:07:46 at
> org.junit.platform.engine.support.hierarchical.NodeTestTask.execute(NodeTestTask.java:95)
> Mar 14 02:07:46 at
> org.junit.platform.engine.support.hierarchical.ForkJoinPoolHierarchicalTestExecutorService$ExclusiveTask.compute(ForkJoinPoolHierarchicalTestExecutorService.java:185)
> Mar 14 02:07:46 at
> java.util.concurrent.RecursiveAction.exec(RecursiveAction.java:189)
> Mar 14 02:07:46 at
> java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:289)
> Mar 14 02:07:46 at
> java.util.concurrent.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1056)
> Mar 14 02:07:46 at
> java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1692)
> Mar 14 02:07:46 at
> java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:175)
> Mar 14 02:07:46 Caused by: java.util.concurrent.ExecutionException:
> org.apache.kafka.common.errors.TopicExistsException: Topic
> 'kafka-single-topic-1095096269466403022' already exists.
> Mar 14 02:07:46 at
> java.util.concurrent.CompletableFuture.reportGet(CompletableFuture.java:357)
> Mar 14 02:07:46 at
> java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1908)
> Mar 14 02:07:46 at
> org.apache.kafka.common.internals.KafkaFutureImpl.get(KafkaFutureImpl.java:165)
> Mar 14 02:07:46 at
> org.apache.flink.connector.kafka.sink.testutils.KafkaSinkExternalContext.createTopic(KafkaSinkExternalContext.java:101)
> Mar 14 02:07:46 ... 110 more
> Mar 14 02:07:46 Caused by:
> org.apache.kafka.common.errors.TopicExistsException: Topic
> 'kafka-single-topic-1095096269466403022' already exists.
> {code}
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=47127&view=logs&j=aa18c3f6-13b8-5f58-86bb-c1cffb239496&t=502fb6c0-30a2-5e49-c5c2-a00fa3acb203&l=36477
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
