[
https://issues.apache.org/jira/browse/FLINK-10603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16658177#comment-16658177
]
vinoyang edited comment on FLINK-10603 at 10/21/18 11:33 AM:
-------------------------------------------------------------
The reason for this issue is due to the increase in the timeout of
testFailOnNoBroker (from 60 seconds to 120 seconds). The timeout for extending
the method was originally because it needed access to the Kafka client API:
partitionsFor. In kafka client 2.0 its default timeout is 60s.
According to the official description of the relevant configuration, the
timeout period is determined by the configuration item
([#max.block.ms]https://kafka.apache.org/documentation/). So, we tried to
reduce the configuration to 30s.
was (Author: yanghua):
The reason for this issue is due to the increase in the timeout of
testFailOnNoBroker (from 60 seconds to 120 seconds). The timeout for extending
the method was originally because it needed access to the Kafka client API:
partitionsFor. In kafka client 2.0 its default timeout is 60s.
According to the official description of the relevant configuration, the
timeout period is determined by the configuration item (max.block.ms). So, we
tried to reduce the configuration to 30s.
> Reduce kafka test duration
> --------------------------
>
> Key: FLINK-10603
> URL: https://issues.apache.org/jira/browse/FLINK-10603
> Project: Flink
> Issue Type: Sub-task
> Components: Kafka Connector, Tests
> Affects Versions: 1.7.0
> Reporter: Chesnay Schepler
> Assignee: vinoyang
> Priority: Major
>
> The tests for the modern kafka connector take more than 10 minutes which is
> simply unacceptable.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
