[
https://issues.apache.org/jira/browse/FLINK-19014?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17203768#comment-17203768
]
Robert Metzger edited comment on FLINK-19014 at 9/29/20, 8:08 AM:
------------------------------------------------------------------
Reduced the time to launch a flink job a tiny bit in:
https://github.com/apache/flink/commit/b4ac5c626877d6e78ba01a36b067764671621c29
I would leave this ticket open. There are quite a few items that contribute a
certain baseline of time to the e2e test duration:
Examples:
- "jobmanager.sh:parseJmJvmArgsAndExportLogs": takes roughly 0.5 seconds on
modern hardware – it starts a JVM
- sourcing the "config.sh" script takes 0.1 seconds (it is sourced multiple
times
- getting the java version takes another 0.15 seconds (REMOVED NOW)
- submitting a Flink job takes ~5 seconds
- waiting till the job is running ~2 seconds
was (Author: rmetzger):
Reduced the time to launch a flink job a tiny bit in:
https://github.com/apache/flink/commit/b4ac5c626877d6e78ba01a36b067764671621c29
> Investigate minimum e2e test duration
> -------------------------------------
>
> Key: FLINK-19014
> URL: https://issues.apache.org/jira/browse/FLINK-19014
> Project: Flink
> Issue Type: Task
> Components: Tests
> Reporter: Chesnay Schepler
> Priority: Major
> Labels: pull-request-available
>
> Currently, the minimum time for an e2e test is roughly 30 seconds.
> This even applies to tests that start a tiny cluster and only run a WordCount.
> It would be good to understand what exactly causes these tests to run for
> such a long time.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
