-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
start to refactor persistence layer to prepare for direct path #30265
Conversation
Checks are failing. Will not request review until checks are succeeding. If you'd like to override that behavior, comment |
Assigning reviewers. If you would like to opt out of this review, comment R: @robertwb added as fallback since no labels match configuration Available commands:
The PR bot will only process comments in the main thread (not review comments). |
4b9e05a
to
c74f23f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you merge with the conflicts? Otherwise looking good
0b741de
to
0bce6d7
Compare
ready for another look @scwhittle |
Run Java Precommit |
Run Java PreCommit |
Looks like this assert failed in test: Line 3355 in 0bce6d7
Could be flaky if doesn't wait enough to get commit or it could be an indication that the heartbeat response plumbing isn't working. |
@scwhittle ran locally and it passed. looks we depend on sleep() in the test, and i wonder if that leads to flakiness in the GitHub actions environment?
also kind of strange that we are waiting for 2 commits but are asserting that there is only 1 commit. But looks like this is a flaky test failure |
Run Java PreCommit |
That test expects 1 commit but meant to wait for some extra time to make sure there were not 2. |
createWindmillServerStub( | ||
options, | ||
clientId, | ||
new WorkHeartbeatResponseProcessor( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't see where this is setup if the forTesting method is used.
Are you sure this isn't the cause of the test failure?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
figured it out looks like the work isn't being populated in the computation map will fix it
thanks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fixed
/** Decorates calls to Streaming Engine persistence by tracking metrics on RPCs. */ | ||
@Internal | ||
@ThreadSafe | ||
public final class PersistentStateReadMetricsTracker { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This appears unused in this PR
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm going to remove it for now to merge the rest to avoid review delay.
…ache/beam/runners/dataflow/worker/windmill/state/PersistentStateReadMetricsTracker.java rm unused PersistentStateReadMetricsTracker
Change classes that explicitly inject a
MetricTrackingWindmillServerStub
to take in a Function.This will give flexibility in later refactoring as we apply different ways to fetch the data without MetricTrackingWindmillServerStub.
Add
PersistentStateReadMetricsTracker
, which is similar toMetricTrackingWindmillServerStub
but allows callers to inject aGetDataStream
(which is necessary for direct path since the calls need to be appropriately routed) and is streaming engine specific.R: @scwhittle
Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:
addresses #123
), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, commentfixes #<ISSUE NUMBER>
instead.CHANGES.md
with noteworthy changes.See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)
See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.