[
https://issues.apache.org/jira/browse/FLINK-22198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17400280#comment-17400280
]
Qingsheng Ren commented on FLINK-22198:
---------------------------------------
This is another instance from my own Azure pipeline, which proved my assumption
before in FLINK-22146:
[https://dev.azure.com/renqs/Apache%20Flink/_build/results?buildId=65&view=logs&j=d543d572-9428-5803-a30c-e8e09bf70915&t=4e4199a3-fbbb-5d5b-a2be-802955ffb013]
Basically I add a timer to print Kafka topic partition status if the test hangs
for 5 minutes. And the log showed that the starting offset of the partition is
not 0, so test hanged because it couldn't receive expected messages with offset
0-3.
{code:java}
19:54:22,603 [ Debug Logging Timer] INFO
org.apache.flink.streaming.connectors.kafka.table.KafkaTableITCase [] -
TopicPartition "key_partial_value_topic_avro-0": starting offset: 4, stopping
offset: 4
{code}
I'm still investigating why this could happen on broker side. Here is a PR for
redirecting KafkaContainer's output to log4j and printing log if test hangs:
[https://github.com/apache/flink/pull/16860]
> KafkaTableITCase hang.
> ----------------------
>
> Key: FLINK-22198
> URL: https://issues.apache.org/jira/browse/FLINK-22198
> Project: Flink
> Issue Type: Bug
> Components: Connectors / Kafka
> Affects Versions: 1.14.0, 1.12.4
> Reporter: Guowei Ma
> Assignee: Qingsheng Ren
> Priority: Blocker
> Labels: pull-request-available, stale-blocker, test-stability
> Fix For: 1.14.0
>
>
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=16287&view=logs&j=c5f0071e-1851-543e-9a45-9ac140befc32&t=1fb1a56f-e8b5-5a82-00a0-a2db7757b4f5&l=6625
> There is no any artifacts.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
