-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
[runtime] Use CollectCoordinationResponse as a wrapper of CoordinationResponse #2744
Closed
2 tasks done
Tracked by
#2600
Labels
Comments
PatrickRen
added
enhancement
New feature or request
【3.0】
task for Flink CDC 3.0
labels
Nov 23, 2023
PatrickRen
added a commit
to PatrickRen/flink-cdc
that referenced
this issue
Nov 23, 2023
…ationResponse The reason we do this is that there is potentially a bug in Flink RPC system, that CoordinationResponse can only be deserialized by AppClassloader instead of user code classloader, so we can't use customize CoordinationResponse class in RPCs (will lead to ClassNotFoundException). As CollectCoordinationResponse is predefined in Flink and shipped in flink-dist, it will be always visible to AppClassloader, and we use its payload for holding the actual serialized custom CoordinationResponse. This closes apache#2744
PatrickRen
added a commit
to PatrickRen/flink-cdc
that referenced
this issue
Nov 23, 2023
…ationResponse The reason we do this is that there is potentially a bug in Flink RPC system, that CoordinationResponse can only be deserialized by AppClassloader instead of user code classloader, so we can't use customize CoordinationResponse class in RPCs (will lead to ClassNotFoundException). As CollectCoordinationResponse is predefined in Flink and shipped in flink-dist, it will be always visible to AppClassloader, and we use its payload for holding the actual serialized custom CoordinationResponse. This closes apache#2744
PatrickRen
added a commit
to PatrickRen/flink-cdc
that referenced
this issue
Nov 23, 2023
…ationResponse The reason we do this is that there is potentially a bug in Flink RPC system, that CoordinationResponse can only be deserialized by AppClassloader instead of user code classloader, so we can't use customize CoordinationResponse class in RPCs (will lead to ClassNotFoundException). As CollectCoordinationResponse is predefined in Flink and shipped in flink-dist, it will be always visible to AppClassloader, and we use its payload for holding the actual serialized custom CoordinationResponse. This closes apache#2744
PatrickRen
added a commit
to PatrickRen/flink-cdc
that referenced
this issue
Nov 23, 2023
…ationResponse The reason we do this is that there is potentially a bug in Flink RPC system, that CoordinationResponse can only be deserialized by AppClassloader instead of user code classloader, so we can't use customize CoordinationResponse class in RPCs (will lead to ClassNotFoundException). As CollectCoordinationResponse is predefined in Flink and shipped in flink-dist, it will be always visible to AppClassloader, and we use its payload for holding the actual serialized custom CoordinationResponse. This closes apache#2744
e-mhui
pushed a commit
to e-mhui/flink-cdc-connectors
that referenced
this issue
Dec 2, 2023
…ationResponse The reason we do this is that there is potentially a bug in Flink RPC system, that CoordinationResponse can only be deserialized by AppClassloader instead of user code classloader, so we can't use customize CoordinationResponse class in RPCs (will lead to ClassNotFoundException). As CollectCoordinationResponse is predefined in Flink and shipped in flink-dist, it will be always visible to AppClassloader, and we use its payload for holding the actual serialized custom CoordinationResponse. This closes apache#2744
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Search before asking
Motivation
The reason we do this is that there is potentially a bug in Flink RPC system, that CoordinationResponse ca
n only be deserialized by AppClassloader instead of user code classloader, so we can't use customize Coordinat
ionResponse class in RPCs (will lead to ClassNotFoundException). As CollectCoordinationResponse is predefined
in Flink and shipped in flink-dist, it will be always visible to AppClassloader, and we use its payload for ho
lding the actual serialized custom CoordinationResponse.
Solution
No response
Alternatives
No response
Anything else?
No response
Are you willing to submit a PR?
The text was updated successfully, but these errors were encountered: