Skip to content

Conversation

rkhachatryan
Copy link
Contributor

@rkhachatryan rkhachatryan commented May 27, 2020

This PR depends on #12292 which should be merged first

What is the purpose of the change

With Unaligned Checkpoints enabled, channel state is written to the file system. If the underlying state handle is shared between multiple handles, they should report their size according to offsets.

Currently, each handle reports the size of the underlying handle, therefore multiplying total state size in reports.

This PR stores state size explicitly in each handle.

Verifying this change

This change added tests and can be verified as follows: added ChannelStateCheckpointWriterTest.testFileHandleSize.

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: 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

…tRecordingOffsets

1. Set writer position in NetworkBuffer passed to ChannelStateCheckpointWriter.write
2. Reduce state size to fit in the configured MemoryCheckpointOutputStream
… deserializer

Motivation:
1. add a method that deserializes and then serializes data
2. simplify
…o JM

Before this commit, if Unaligned checkpoints are enabled,
channel state is written as state handles. Each channel
has a handle and each such handle references the same
underlying streamStateHandle (this is done to have
a single file per subtask).

But, if the state is less then state.backend.fs.memory-threshold,
the data is sent directly to JM as a byteStreamHandle.
This causes each channel state handle to hold the whole subtask state.

This change solves this by extracting relevant potions
of the underlying handles if they are byteStreamHandles.
Store state size explicitly because underlying state
handle may be shared.
@rkhachatryan rkhachatryan marked this pull request as draft May 27, 2020 14:54
@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.

Automated Checks

Last check on commit 7ec6577 (Wed May 27 14:55:49 UTC 2020)

Warnings:

  • No documentation files were touched! Remember to keep the Flink docs up to date!
  • This pull request references an unassigned Jira ticket. According to the code contribution guide, tickets need to be assigned before starting with the implementation work.

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

@flinkbot
Copy link
Collaborator

flinkbot commented May 27, 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

@pnowojski
Copy link
Contributor

Can you ping me once azure is green?

@rkhachatryan rkhachatryan marked this pull request as ready for review May 27, 2020 17:26
@rkhachatryan
Copy link
Contributor Author

ping @pnowojski )

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.

4 participants