[
https://issues.apache.org/jira/browse/FLINK-10720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16673442#comment-16673442
]
ASF GitHub Bot commented on FLINK-10720:
----------------------------------------
StefanRRichter 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-435449615
@tillrohrmann that depends how we want to interpret the result. Right now,
the test is passed when it somehow manages to do one successsful recovery. If
we want to test that the first recovery must already be successful, we could
limit the number of allowed failed attempts to 1. Would you prefer to enforce
succesful recovery in the first attempt?
----------------------------------------------------------------
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:
us...@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)
