Navigation Menu

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-14843][e2e] Refactor bucketing sink test to make it more stable and comprehensible #10685

Closed
wants to merge 2 commits into from

Conversation

banmoy
Copy link
Contributor

@banmoy banmoy commented Dec 25, 2019

What is the purpose of the change

Refactor bucketing sink e2e test to make it more stable and comprehensible.

Brief change log

  • For BucketingSinkTestProgram, set inactiveBucketCheckInterval and inactiveBucketThreshold to 2000 and 4000 respectively
  • only count records in part-* files to get total valid data
  • remove "sleep 10" between two failover to make it comprehensible

Verifying this change

Existing e2e test.

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, 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)

@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 18d9268 (Wed Dec 25 08:59:14 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

@flinkbot
Copy link
Collaborator

flinkbot commented Dec 25, 2019

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

@banmoy
Copy link
Contributor Author

banmoy commented Dec 25, 2019

@flinkbot run travis

@banmoy
Copy link
Contributor Author

banmoy commented Dec 26, 2019

@flinkbot run azure

@banmoy
Copy link
Contributor Author

banmoy commented Jan 3, 2020

@flinkbot run travis

@banmoy
Copy link
Contributor Author

banmoy commented Jan 7, 2020

@kl0u Can you help to review this PR? Thanks

@aljoscha
Copy link
Contributor

aljoscha commented Jan 8, 2020

@kl0u is currently on vacation but I'm sure he'll have a look once he's back.

@kl0u kl0u self-assigned this Jan 15, 2020
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.

Thanks for working on this @banmoy ! In general changes look good. I had some minor comments. Do you think that the same change can be applied to the StreamingFileSink end-to-end test?

@@ -74,8 +74,8 @@ public static void main(String[] args) throws Exception {
.setBucketer(new KeyBucketer())
.setBatchSize(Long.MAX_VALUE)
.setBatchRolloverInterval(Long.MAX_VALUE)
.setInactiveBucketCheckInterval(Long.MAX_VALUE)
.setInactiveBucketThreshold(Long.MAX_VALUE);
.setInactiveBucketCheckInterval(2000)
Copy link
Contributor

Choose a reason for hiding this comment

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

Why not setting the values to something smaller so that the test runs faster?

@@ -27,7 +27,7 @@ function get_total_number_of_valid_lines {
# this method assumes that pending files contain valid data.
Copy link
Contributor

Choose a reason for hiding this comment

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

The comment is now invalid as we do not assume that pending files have valid data anymore.

@@ -150,7 +148,7 @@ wait_job_terminal_state ${JOB_ID} "CANCELED"
echo "Job $JOB_ID was cancelled, time to verify"

# get all lines in pending or part files
Copy link
Contributor

Choose a reason for hiding this comment

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

The comment is now invalid as we do not get the lines in the pending files.

@banmoy
Copy link
Contributor Author

banmoy commented Jan 15, 2020

@kl0u Thanks for your review. In StreamingFileSink end-to-end test, OnCheckpointRollingPolicy ensures in-progress part files will be rolled to part files finally, so I think there is no need to enable inactive check. I update the PR, and please have a look.

@banmoy
Copy link
Contributor Author

banmoy commented Jan 16, 2020

travis on ce56c02 failed with BackPressureITCase which is tracked in FLINK-15247, and rerun travis.

@banmoy
Copy link
Contributor Author

banmoy commented Jan 16, 2020

@flinkbot run travis

@kl0u
Copy link
Contributor

kl0u commented Jan 16, 2020

Thanks for the work @banmoy ! Merged it

@kl0u kl0u closed this Jan 16, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
5 participants