Skip to content

Conversation

@rkhachatryan
Copy link
Contributor

What is the purpose of the change

This PR includes changes from #13040 and some refactorings of new and existing code.

Verifying this change

Changes for backpressure tested by new ZooKeeperCompletedCheckpointStoreITCase.testChekpointingPausesAndResumeWhenTooManyCheckpoints test

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, Kubernetes/Yarn/Mesos, ZooKeeper: yes
  • 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

echauchot and others added 4 commits October 8, 2020 15:48
…e for asynchronous checkpoints cleaning via the ioExecutor. This class counts the number of checkpoints to clean and reports it to CheckpointRequestDecider. Add a test for too many checkpoints to clean.
…nt classes

Pass CheckpointsCleaner and postCleanup as arguments
instead of storing them in Checkpoints classes as callbacks.
Pass Executor as an argument instead of storing it as a field.
@flinkbot
Copy link
Collaborator

flinkbot commented Oct 8, 2020

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 82386f6 (Fri May 28 07:00:20 UTC 2021)

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.

Details
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

@flinkbot
Copy link
Collaborator

flinkbot commented Oct 8, 2020

CI report:

Bot commands The @flinkbot bot supports the following commands:
  • @flinkbot run travis re-run the last Travis build
  • @flinkbot run azure re-run the last Azure build

@etienne-chauchot
Copy link

etienne-chauchot commented Oct 12, 2020

@rkhachatryan I don't see my ITest commit in this history. Does this mean that you don't want to merge this part of the code or is it just that the commit was forgotten?

Copy link
Contributor

@pnowojski pnowojski left a comment

Choose a reason for hiding this comment

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

I think @etienne-chauchot your test was squashed with the commit that was adding the feature.

@etienne-chauchot
Copy link

I think @etienne-chauchot your test was squashed with the commit that was adding the feature.

Ok fair enough

Copy link
Contributor

@pnowojski pnowojski left a comment

Choose a reason for hiding this comment

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

LGTM, @rkhachatryan could you squash the fixup commit?

…tsCleaner

Replace cleanup Runnable with a direct call to CheckpointsCleaner.
@rkhachatryan rkhachatryan force-pushed the f17073-refactor-fixup branch from 2d4a962 to 82386f6 Compare October 14, 2020 10:18
@rkhachatryan
Copy link
Contributor Author

rkhachatryan commented Oct 14, 2020

@pnowojski, I squashed the commit but the build failed.
The reason is unrelated: FLINK-19619 (both public and private repos).

@pnowojski
Copy link
Contributor

Thanks for the contribution both @rkhachatryan and @etienne-chauchot . Merging.

* @param jobStatus Job state on shut down
*/
void shutdown(JobStatus jobStatus) throws Exception;
void shutdown(JobStatus jobStatus, CheckpointsCleaner checkpointsCleaner, Runnable postCleanup) 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.

Why do we need the postCleanup? In the current code base I couldn't find a single usage where we don't pass () -> {} @rkhachatryan and @pnowojski? If this is not needed, can we get rid of it? I think it does not make a very nice API with the no-ops.

Moreover, it would be nice if we could update the JavaDocs if we change the signature of interfaces.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

postCleanup is used by checkpointsCleaner but not in case of shutting down. I agree, it should be removed (by pushing down to DefaultCompletedCheckpointStore) and javadoc added. My bad.
I've created FLINK-20847 to address this.

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.

7 participants