how can we know the expected size for which it is failing?
If you did not configure akka.framesize yourself then it is set to the
documented default value. See the configuration documentation for the
release you are using.
> Does the operator state have any impact on the expected Akka frame size?
If you are using the MemoryStateBackend, yes. Otherwise, the impact of
using any form of state on the framesize should be negligible.
> What is the impact of increasing it?
Increase in memory consumption, probably around 1-2x the increased
amount. (So, increase it my 1mb, memory usages goes up by 1-2 mb)
On 9/18/2020 9:50 AM, shravan wrote:
Hi,
This is in continuation to an already raised request, (had replied to the
same thread but couldn't get any response yet, hence posting a new request)
http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/The-rpc-invocation-size-exceeds-the-maximum-akka-framesize-when-the-job-was-re-submitted-td37507.html
We are observing the same error as well with regard to "The rpc invocation
size exceeds the maximum akka framesize.", and have follow-up questions on
the same.
Why we face this issue, how can we know the expected size for which it is
failing? The error message does not indicate that. Does the operator state
have any impact on the expected Akka frame size? What is the impact of
increasing it?
Awaiting a response.
Regards,
Shravan
--
Sent from: http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/
