You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/06/14 21:42:00 UTC
[jira] [Commented] (KAFKA-5450) Scripts to startup Connect in
system tests have too short a timeout
[ https://issues.apache.org/jira/browse/KAFKA-5450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16049697#comment-16049697 ]
ASF GitHub Bot commented on KAFKA-5450:
---------------------------------------
GitHub user rhauch opened a pull request:
https://github.com/apache/kafka/pull/3344
KAFKA-5450 Increased timeout of Connect system test utilities
Increased the timeout from 30sec to 60sec. When running the system tests with packaged Kafka, Connect workers can take about 30seconds to start.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/rhauch/kafka KAFKA-5450
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/3344.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #3344
----
commit 0f1f9f98b175e06373f1f4e5edcb009903b22e6e
Author: Randall Hauch <rh...@gmail.com>
Date: 2017-06-14T21:41:11Z
KAFKA-5450 Increased timeout of Connect system test utilities
Increased the timeout from 30sec to 60sec. When running the system tests with packaged Kafka, Connect workers can take about 30seconds to start.
----
> Scripts to startup Connect in system tests have too short a timeout
> -------------------------------------------------------------------
>
> Key: KAFKA-5450
> URL: https://issues.apache.org/jira/browse/KAFKA-5450
> Project: Kafka
> Issue Type: Bug
> Components: system tests
> Affects Versions: 0.11.0.0
> Reporter: Randall Hauch
> Assignee: Randall Hauch
> Fix For: 0.11.1.0
>
>
> When the system tests start up a Kafka Connect standalone or distributed worker, the utility starts the process, and if the worker does not start up within 30 seconds the utility considers it a failure and stops everything.
> This is often sufficient when running the system tests against the source code, as the CLASSPATH for Connect includes only the Kafka Connect runtime JARs (in addition to all of the connector dirs). However, when running the system tests against the packaged form of Kafka, the CLASSPATH for Connect includes all of the Apache Kafka JARs (in addition to all of the connector dirs). This increases the total number of JARs that have to be scanned by almost 75% and increases the time required to scan all of the JARs nearly doubles from ~14sec to ~26sec. (Some of the additional JARs are likely larger and take longer to scan than those JARs in Connect or the connectors.)
> As a result, the 30 second timeout is often not quite sufficient for the Connect system test utility and should be increased to 60 seconds. This shouldn't noticeably increase the time of most system tests, since 30 seconds was nearly sufficient anyway; it will increase the duration of the tests where does fail to start, but that ideally won't happen much. :-)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)