flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-10720) Add stress deployment end-to-end test
Date Mon, 05 Nov 2018 11:17:00 GMT

    [ https://issues.apache.org/jira/browse/FLINK-10720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16674987#comment-16674987
] 

ASF GitHub Bot commented on FLINK-10720:
----------------------------------------

tillrohrmann commented on issue #6994: [FLINK-10720][tests] Add deployment end-to-end stress
test with many …
URL: https://github.com/apache/flink/pull/6994#issuecomment-435839464
 
 
   Maybe it's best to say that we set the attempt number to a low value (something like 3
or so) in order to tolerate some failures but require that this should be quickly resolved
(for the sake of test stability).

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> Add stress deployment end-to-end test
> -------------------------------------
>
>                 Key: FLINK-10720
>                 URL: https://issues.apache.org/jira/browse/FLINK-10720
>             Project: Flink
>          Issue Type: Sub-task
>          Components: E2E Tests
>    Affects Versions: 1.7.0
>            Reporter: Till Rohrmann
>            Assignee: Stefan Richter
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.7.0
>
>
> In order to test Flink's scalability, I suggest to add an end-to-end test which tests
the deployment of a job which is very demanding. The job should have large {{TaskDeploymentDescriptors}}
(e.g. a job using union state or having a high degree of parallelism). That way we can test
that the serialization overhead of the TDDs does not affect the health of the cluster (e.g.
heartbeats are not affected because the serialization does not happen in the main thread).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message