GitHub user tillrohrmann opened a pull request:
https://github.com/apache/flink/pull/2365
[FLINK-4383] [rpc] Eagerly serialize remote rpc invocation messages
This PR introduces an eager serialization for remote rpc invocation
messages.
That way it is possible to check whether the message is serializable and
whether it exceeds the maximum allowed akka frame size. If either of these
constraints is violated, a proper exception is thrown instead of simply
swallowing the exception as Akka does it.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/tillrohrmann/flink rpcSerializability
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/2365.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2365
----
commit 7dcac59723130bd9a77f34cea574f8d7303305f8
Author: Till Rohrmann <[email protected]>
Date: 2016-08-12T08:32:30Z
[FLINK-4383] [rpc] Eagerly serialize remote rpc invocation messages
This PR introduces an eager serialization for remote rpc invocation
messages.
That way it is possible to check whether the message is serializable and
whether it exceeds the maximum allowed akka frame size. If either of these
constraints is violated, a proper exception is thrown instead of simply
swallowing the exception as Akka does it.
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---