-
Notifications
You must be signed in to change notification settings - Fork 13.8k
[FLINK-38804][runtime] Ensure channelStateWriter is closed after the inputGates #27375
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
base: master
Are you sure you want to change the base?
Conversation
62e89f3 to
2333f28
Compare
2333f28 to
0469fec
Compare
|
@flinkbot run azure |
|
|
||
| ChannelStateWriter getChannelStateWriter(); | ||
|
|
||
| void setChannelStateWriter(ChannelStateWriter channelStateWriter); |
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.
nit: the pattern seems to be the define the set then the get method.
| } | ||
|
|
||
| public void setChannelStateWriter(ChannelStateWriter channelStateWriter) { | ||
| checkState(this.channelStateWriter == null, "Can not set channelStateWriter twice!"); |
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.
Do we know if we can get here with an existing one present - if so can we check for that situation earlier? I am happy with the check to be safe - but wanted to ask this question.
nit: Can not -> Cannot
| */ | ||
| private UserCodeClassLoader userCodeClassLoader; | ||
|
|
||
| @Nullable private volatile ChannelStateWriter channelStateWriter; |
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 suggest a comment to describe why this needs to be volatile
What is the purpose of the change
(For example: This pull request makes task deployment go through the blob server, rather than through RPC. That way we avoid re-transferring them on each deployment (during recovery).)
Brief change log
(for example:)
Verifying this change
Please make sure both new and modified tests in this PR follow the conventions for tests defined in our code quality guide.
(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)
Does this pull request potentially affect one of the following parts:
@Public(Evolving): (yes / no)Documentation