[
https://issues.apache.org/jira/browse/FLINK-13663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16905441#comment-16905441
]
Alex commented on FLINK-13663:
------------------------------
FYI, the {{curl}} retries were added as an attempt to address the issue
described in FLINK-12773.
We can try to increase number of retries/retry timeout, but it's possible that
this won't help much.
Instead (or in parallel), my proposal would be to try to cache and share the
downloaded Kafka distribution among multiple e2e test runs.
There is a PR by [~Zentol] (https://github.com/apache/flink/pull/7605) which
conceptually does it. Personally, I find the PR as relatively big and it's
possible to implement the caching logic as some script with low effort.
> SQL Client end-to-end test for modern Kafka failed on Travis
> ------------------------------------------------------------
>
> Key: FLINK-13663
> URL: https://issues.apache.org/jira/browse/FLINK-13663
> Project: Flink
> Issue Type: Bug
> Components: Connectors / Kafka, Table SQL / Client, Tests
> Affects Versions: 1.9.0, 1.10.0
> Reporter: Till Rohrmann
> Priority: Critical
> Labels: test-stability
>
> The {{SQL Client end-to-end test for modern Kafka}} failed on Travis because
> it could not download
> {{https://archive.apache.org/dist/kafka/0.11.0.2/kafka_2.11-0.11.0.2.tgz}}.
> Maybe we could add a similar retry logic as with the Kinesis end-to-end test
> FLINK-13599.
> https://api.travis-ci.org/v3/job/569262834/log.txt
> https://api.travis-ci.org/v3/job/569262828/log.txt
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
