Skip to content

Conversation

@tillrohrmann
Copy link
Contributor

What is the purpose of the change

Port RecoveryITCase to new code base.

This PR is based on #7676.

Brief change log

  • "recover a task manager failure" --> TaskExecutorITCase#testJobRecoveryWithFailingTaskExecutor
  • "recover once failing forward job" --> JobRecoveryITCase#testTaskFailureRecovery
  • "recover once failing forward job with slot sharing" --> JobRecoveryITCase#testTaskFailureWithSlotSharingRecovery

Verifying this change

  • Executed ported tests repeatedly

Does this pull request potentially affect one of the following parts:

  • Dependencies (does it add or upgrade a dependency): (no)
  • The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
  • The serializers: (no)
  • The runtime per-record code paths (performance sensitive): (no)
  • Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Yarn/Mesos, ZooKeeper: (no)
  • The S3 file system connector: (no)

Documentation

  • Does this pull request introduce a new feature? (no)
  • If yes, how is the feature documented? (not applicable)

@flinkbot
Copy link
Collaborator

Thanks a lot for your contribution to the Apache Flink project. I'm the @flinkbot. I help the community
to review your pull request. We will use this comment to track the progress of the review.

Review Progress

  • ❌ 1. The [description] looks good.
  • ❌ 2. There is [consensus] that the contribution should go into to Flink.
  • ❔ 3. Needs [attention] from.
  • ❌ 4. The change fits into the overall [architecture].
  • ❌ 5. Overall code [quality] is good.

Please see the Pull Request Review Guide for a full explanation of the review process.

Details

Bot commands The @flinkbot bot supports the following commands:
  • @flinkbot approve description to approve the 1st aspect (similarly, it also supports the consensus, architecture and quality keywords)
  • @flinkbot approve all to approve all aspects
  • @flinkbot attention @username1 [@username2 ..] to require somebody's attention
  • @flinkbot disapprove architecture to remove an approval

*/
@Test
public void testNewTaskExecutorJoinsCluster() throws Exception {
public void testCleanClusterStateAfterTaskExecutorTermination() throws Exception {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The name is not very intuitive, I think testJobReExecutionAfterTaskExecutorTermination would be better.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good idea. I will apply the changes.

CommonTestUtils.waitUntilCondition(
jobIsRunning(() -> miniCluster.getExecutionGraph(jobGraph.getJobID())),
Deadline.fromNow(TESTING_TIMEOUT),
20L);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is a bug in waitUntilCondition which leads to 20 being ignored.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch. Will fix it while merging this PR.

@tillrohrmann
Copy link
Contributor Author

Thanks for the review @GJL. I'll address your comment while merging this PR.

…ception, Deadline, long)

Properly pass the retryIntervalMillis to the sleep call.
- "recover a task manager failure" --> TaskExecutorITCase#testJobRecoveryWithFailingTaskExecutor
- "recover once failing forward job" --> JobRecoveryITCase#testTaskFailureRecovery
- "recover once failing forward job with slot sharing" --> JobRecoveryITCase#testTaskFailureWithSlotSharingRecovery
Increase the retry interval for TaskExecutorITCase and ZooKeeperLeaderElectionITCase
since they take so long that the low retry interval won't have a big effect apart
from a higher CPU load.
tillrohrmann added a commit to tillrohrmann/flink that referenced this pull request Feb 14, 2019
- "recover a task manager failure" --> TaskExecutorITCase#testJobRecoveryWithFailingTaskExecutor
- "recover once failing forward job" --> JobRecoveryITCase#testTaskFailureRecovery
- "recover once failing forward job with slot sharing" --> JobRecoveryITCase#testTaskFailureWithSlotSharingRecovery

This closes apache#7683.
@asfgit asfgit closed this in 2f93866 Feb 14, 2019
@tillrohrmann tillrohrmann deleted the FLINK-11486 branch February 14, 2019 12:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants