[ 
https://issues.apache.org/jira/browse/FLINK-8161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sergey Nuyanzin reopened FLINK-8161:
------------------------------------

Looks like it happened again
Also I downloaded logs mentioned in failed travis job 
{quote}
 Uploading to transfer.sh
https://transfer.sh/JspTz/24547.10.tar.gz
{quote}

based on them it looks like there was a connectivity issue with one of the 
ApplicationMaster 
as log yarn-tests/container_1526608500321_0007_01_000001/job-manager.log is 
full of
{quote} 2018-05-18 01:56:49,448 WARN  
akka.remote.transport.netty.NettyTransport                    - Remote 
connection to [null] failed with java.net.ConnectException: Connection refused: 
travis-job-2a2afdc5-7bf8-4597-946e-16551a5ebbc4/127.0.1.1:43980
2018-05-18 01:56:49,449 WARN  akka.remote.ReliableDeliverySupervisor            
            - Association with remote system 
[akka.tcp://flink@travis-job-2a2afdc5-7bf8-4597-946e-16551a5ebbc4:43980] has 
failed, address is now gated for [50] ms. Reason: [Association failed with 
[akka.tcp://flink@travis-job-2a2afdc5-7bf8-4597-946e-16551a5ebbc4:43980]] 
Caused by: [Connection refused: 
travis-job-2a2afdc5-7bf8-4597-946e-16551a5ebbc4/127.0.1.1:43980]
{quote}
very strange thing 



> Flakey YARNSessionCapacitySchedulerITCase on Travis
> ---------------------------------------------------
>
>                 Key: FLINK-8161
>                 URL: https://issues.apache.org/jira/browse/FLINK-8161
>             Project: Flink
>          Issue Type: Bug
>          Components: Tests, YARN
>    Affects Versions: 1.5.0
>            Reporter: Till Rohrmann
>            Assignee: Till Rohrmann
>            Priority: Critical
>              Labels: test-stability
>             Fix For: 1.5.0
>
>
> The {{YARNSessionCapacitySchedulerITCase}} spuriously fails on Travis because 
> it now contains {{2017-11-25 22:49:49,204 WARN  
> akka.remote.transport.netty.NettyTransport                    - Remote 
> connection to [null] failed with java.nio.channels.NotYetConnectedException}} 
> from time to time in the logs. I suspect that this is due to switching from 
> Flakka to Akka 2.4.0. In order to solve this problem I propose to add this 
> log statement to the whitelisted log statements.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to