[ 
https://issues.apache.org/jira/browse/FLINK-4377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16046530#comment-16046530
 ] 

Nico Kruber commented on FLINK-4377:
------------------------------------

As to whether and how we could at least react to an 
{{akka.remote.OversizedPayloadException}}: 
https://groups.google.com/forum/#!topic/akka-user/CIJ-OyaQpEA suggests to 
"suscribe to the eventStream of the ActorSystem to see when there is an 
akka.event.Logging.Error with a OversizedPayloadException as cause" (see 
http://doc.akka.io/docs/akka/2.3.10/scala/event-bus.html#Event_Stream). By 
doing this, we would be able to fail the (sub-)task that caused this error and 
react.

> akka.remote.OversizedPayloadException: Discarding oversized payload
> -------------------------------------------------------------------
>
>                 Key: FLINK-4377
>                 URL: https://issues.apache.org/jira/browse/FLINK-4377
>             Project: Flink
>          Issue Type: Bug
>          Components: DataSet API
>    Affects Versions: 1.1.0
>         Environment: Linux
>            Reporter: Sajeev Ramakrishnan
>
> Dear Team,
>   I was trying to create a hash map with a size around 1 million. Then I 
> encountered the below issue. For smaller maps, I am not seeing any issues.
> akka.remote.OversizedPayloadException: Discarding oversized payload sent to 
> Actor[akka.tcp://flink@localhost:58247/user/$d#458673459]: max allowed size 
> 10485760 bytes, actual size of encoded class 
> org.apache.flink.runtime.messages.JobManagerMessages$JobResultSuccess was 
> 175254213 bytes.
> Regards,
> Sajeev



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to