flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-7845) Netty Exception when submitting batch job repeatedly
Date Mon, 13 Nov 2017 17:53:00 GMT

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

ASF GitHub Bot commented on FLINK-7845:
---------------------------------------

Github user NicoK commented on a diff in the pull request:

    https://github.com/apache/flink/pull/5007#discussion_r150615019
  
    --- Diff: flink-runtime/src/main/java/org/apache/flink/runtime/io/network/netty/NettyMessage.java
---
    @@ -52,8 +52,10 @@
     
     /**
      * A simple and generic interface to serialize messages to Netty's buffer space.
    + *
    + * <p>This class must be public as long as we are using Netty 4.0.x. Please check
FLINK-7845 for more information.
    --- End diff --
    
    actually, Netty 4.0.45 seemed to fix this already


> Netty Exception when submitting batch job repeatedly
> ----------------------------------------------------
>
>                 Key: FLINK-7845
>                 URL: https://issues.apache.org/jira/browse/FLINK-7845
>             Project: Flink
>          Issue Type: Bug
>          Components: Core, Network
>    Affects Versions: 1.3.2
>            Reporter: Flavio Pompermaier
>            Assignee: Piotr Nowojski
>            Priority: Blocker
>             Fix For: 1.4.0
>
>         Attachments: Screen Shot 2017-11-13 at 14.54.38.png
>
>
> We had some problems with Flink and Netty so we wrote a small unit test to reproduce
the memory issues we have in production. It happens that we have to restart the Flink cluster
because the memory is always increasing from job to job. 
> The github project is https://github.com/okkam-it/flink-memory-leak and the JUnit test
is contained in the MemoryLeakTest class (within src/main/test).
> I don't know if this is the root of our problems but at some point, usually around the
28th loop, the job fails with the following exception (actually we never faced that in production
but maybe is related to the memory issue somehow...):
> {code:java}
> Caused by: java.lang.IllegalAccessError: org/apache/flink/runtime/io/network/netty/NettyMessage
> 	at io.netty.util.internal.__matchers__.org.apache.flink.runtime.io.network.netty.NettyMessageMatcher.match(NoOpTypeParameterMatcher.java)
> 	at io.netty.channel.SimpleChannelInboundHandler.acceptInboundMessage(SimpleChannelInboundHandler.java:95)
> 	at io.netty.channel.SimpleChannelInboundHandler.channelRead(SimpleChannelInboundHandler.java:102)
> 	... 16 more
> {code}



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

Mime
View raw message