[
https://issues.apache.org/jira/browse/FLINK-1650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Metzger reopened FLINK-1650:
-----------------------------------
I'm reopening the issue because the exceptions still occur in the current
master.
The flink-yarn-tests are checking the Job and TaskManagers output for
exceptions and fail if they find some.
The found exceptions are in the logfiles uploaded to s3.
For example in
https://flink.a.o.uce.east.s3.amazonaws.com/travis-artifacts/apache/flink/1931/1931.5.tar.gz,
in the {{2.log}}, you'll see the exception.
> Suppress Akka's Netty Shutdown Errors through the log config
> ------------------------------------------------------------
>
> Key: FLINK-1650
> URL: https://issues.apache.org/jira/browse/FLINK-1650
> Project: Flink
> Issue Type: Bug
> Components: other
> Affects Versions: 0.9
> Reporter: Stephan Ewen
> Assignee: Stephan Ewen
> Fix For: 0.9
>
>
> I suggest to set the logging for
> `org.jboss.netty.channel.DefaultChannelPipeline` to error, in order to get
> rid of the misleading stack trace caused by an akka/netty hickup on shutdown.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
