Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FLINK-13124] Don't forward exceptions when finishing SourceStreamTask #9115

Conversation

aljoscha
Copy link
Contributor

What is the purpose of the change

Before, exceptions that occurred after cancelling a source (as the
KafkaConsumer did, for example) would make a job fail when attempting a
"stop-with-savepoint". Now we ignore those exceptions.

Brief change log

  • add a isFinished flag in SourceStreamTask
  • check this flag before re-throwing exceptions

Verifying this change

This change added tests and can be verified as follows:

  • Added unit tests in SourceStreamTaskTest

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

  • Checkpointing, yes, because it fixes stop-with-savepoint

Documentation

  • Does this pull request introduce a new feature? no

Before, exceptions that occurred after cancelling a source (as the
KafkaConsumer did, for example) would make a job fail when attempting a
"stop-with-savepoint". Now we ignore those exceptions.
@aljoscha aljoscha requested a review from kl0u July 15, 2019 11:06
@flinkbot
Copy link
Collaborator

flinkbot commented Jul 15, 2019

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.

Automated Checks

Last check on commit a7f8c3e (Tue Aug 06 15:42:49 UTC 2019)

Warnings:

  • No documentation files were touched! Remember to keep the Flink docs up to date!

Mention the bot in a comment to re-run the automated checks.

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.


The Bot is tracking the review progress through labels. Labels are applied according to the order of the review items. For consensus, approval by a Flink committer of PMC member is required Bot commands
The @flinkbot bot supports the following commands:

  • @flinkbot approve description to approve one or more aspects (aspects: description, consensus, architecture and quality)
  • @flinkbot approve all to approve all aspects
  • @flinkbot approve-until architecture to approve everything until architecture
  • @flinkbot attention @username1 [@username2 ..] to require somebody's attention
  • @flinkbot disapprove architecture to remove an approval you gave earlier

Copy link
Contributor

@kl0u kl0u left a comment

Choose a reason for hiding this comment

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

Merging this on the 1.9

@flinkbot
Copy link
Collaborator

flinkbot commented Jul 15, 2019

CI report:

@kl0u
Copy link
Contributor

kl0u commented Jul 15, 2019

Merge on 1.9.

@aljoscha aljoscha deleted the flink13124-stop-with-savepoint-fix-flink19 branch July 25, 2019 15:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants