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-17014][runtime] Implement PipelinedRegionSchedulingStrategy #11770

Merged

Conversation

zhuzhurk
Copy link
Contributor

What is the purpose of the change

Implement PipelinedRegionSchedulingStrategy which schedules tasks in granularity of pipelined regions. More details see https://cwiki.apache.org/confluence/display/FLINK/FLIP-119+Pipelined+Region+Scheduling.

Brief change log

  • Implemented PipelinedRegionSchedulingStrategy

Verifying this change

  • Added unit tests PipelinedRegionSchedulingStrategyTest

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

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

Documentation

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

@zhuzhurk zhuzhurk requested a review from GJL April 16, 2020 08: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 2577ed1 (Thu Apr 16 08:55:57 UTC 2020)

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

@flinkbot
Copy link
Collaborator

flinkbot commented Apr 16, 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

@GJL GJL self-assigned this Apr 16, 2020
Copy link
Member

@GJL GJL left a comment

Choose a reason for hiding this comment

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

The PipelinedRegionSchedulingStrategy implementation looks neat!


private TestingSchedulerOperations testingSchedulerOperation;

private int parallelism = 2;
Copy link
Member

Choose a reason for hiding this comment

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

Consider making this static final or convert to a local variable.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Ok.


@Override
public Iterable<TestingSchedulingExecutionVertex> getVertices() {
return regionVertices.values();
Copy link
Member

Choose a reason for hiding this comment

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

Consider wrapping it in Collections.unmodifiableCollection() for immutability or returning a copy. Same in getConsumedResults().

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Iterable is considered as unmodifiable so I think it's not very needed.

Copy link
Member

Choose a reason for hiding this comment

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

I don't think that's true, see Iterator#remove()

Copy link
Contributor Author

Choose a reason for hiding this comment

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

You are right. Will wrap it with Collections.unmodifiableCollection().

@@ -78,6 +83,31 @@ public TestingSchedulingResultPartition getResultPartition(final IntermediateRes
return resultPartition;
}

@Override
public Iterable<SchedulingPipelinedRegion> getAllPipelinedRegions() {
return vertexRegions.values().stream().collect(Collectors.toSet());
Copy link
Member

Choose a reason for hiding this comment

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

I think that's the same as new HashSet<>(vertexRegions.values())

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Ok. Let's simplify it.

return vertexRegions.get(vertexId);
}

void generatePipelinedRegions() {
Copy link
Member

Choose a reason for hiding this comment

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

Consider invoking this method lazily in getAllPipelinedRegions() and getPipelinedRegionOfVertex() instead of relying the client (test) to invoke it.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes that would be better.
The only problem is that the regions cannot be refreshed if the topology is changed after invoking getAllPipelinedRegions(). So I will clear the cached regions on any topology changes.

@zhuzhurk zhuzhurk force-pushed the FLINK_17014_pipelined_region_scheduling branch from d8568c4 to 17d9f5e Compare April 20, 2020 08:26
@zhuzhurk zhuzhurk force-pushed the FLINK_17014_pipelined_region_scheduling branch from 17d9f5e to a47976d Compare April 20, 2020 08:49
@zhuzhurk
Copy link
Contributor Author

Will merge it once travis gives green.

@zhuzhurk zhuzhurk merged commit 99cbaa9 into apache:master Apr 21, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants