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

Shane Kumpf commented on YARN-4759:
-----------------------------------

Jenkins slave failed again. Will reattach again.

{code}
============================================================================
============================================================================
                      maven site verification: trunk
============================================================================
============================================================================


cd 
/testptch/hadoop/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager
mvn -Dmaven.repo.local=/home/jenkins/yetus-m2/hadoop-trunk-patch-1 -Ptest-patch 
clean site site:stage > 
/testptch/hadoop/patchprocess/branch-mvnsite-hadoop-yarn-project_hadoop-yarn_hadoop-yarn-server_hadoop-yarn-server-nodemanager.txt
 2>&1
Slave went offline during the build
ERROR: Connection was broken: java.io.IOException: Sorry, this connection is 
closed.
        at 
com.trilead.ssh2.transport.TransportManager.ensureConnected(TransportManager.java:587)
        at 
com.trilead.ssh2.transport.TransportManager.sendMessage(TransportManager.java:660)
        at com.trilead.ssh2.channel.Channel.freeupWindow(Channel.java:407)
        at com.trilead.ssh2.channel.Channel.freeupWindow(Channel.java:347)
        at 
com.trilead.ssh2.channel.ChannelManager.getChannelData(ChannelManager.java:943)
        at 
com.trilead.ssh2.channel.ChannelInputStream.read(ChannelInputStream.java:58)
        at 
com.trilead.ssh2.channel.ChannelInputStream.read(ChannelInputStream.java:79)
        at 
hudson.remoting.FlightRecorderInputStream.read(FlightRecorderInputStream.java:82)
        at 
hudson.remoting.ChunkedInputStream.readHeader(ChunkedInputStream.java:72)
        at 
hudson.remoting.ChunkedInputStream.readUntilBreak(ChunkedInputStream.java:103)
        at 
hudson.remoting.ChunkedCommandTransport.readBlock(ChunkedCommandTransport.java:39)
        at 
hudson.remoting.AbstractSynchronousByteArrayCommandTransport.read(AbstractSynchronousByteArrayCommandTransport.java:34)
        at 
hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48)
Caused by: java.net.SocketException: Broken pipe
        at java.net.SocketOutputStream.socketWrite0(Native Method)
        at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:113)
        at java.net.SocketOutputStream.write(SocketOutputStream.java:159)
        at 
com.trilead.ssh2.crypto.cipher.CipherOutputStream.flush(CipherOutputStream.java:75)
        at 
com.trilead.ssh2.transport.TransportConnection.sendMessage(TransportConnection.java:193)
        at 
com.trilead.ssh2.transport.TransportConnection.sendMessage(TransportConnection.java:107)
        at 
com.trilead.ssh2.transport.TransportManager.sendMessage(TransportManager.java:677)
        at 
com.trilead.ssh2.transport.TransportManager$AsynchronousWorker.run(TransportManager.java:115)
{code}

> Fix signal handling for docker containers
> -----------------------------------------
>
>                 Key: YARN-4759
>                 URL: https://issues.apache.org/jira/browse/YARN-4759
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: yarn
>            Reporter: Sidharta Seethana
>            Assignee: Shane Kumpf
>         Attachments: YARN-4759.001.patch, YARN-4759.002.patch, 
> YARN-4759.003.patch
>
>
> The current signal handling (in the DockerContainerRuntime) needs to be 
> revisited for docker containers. For example, container reacquisition on NM 
> restart might not work, depending on which user the process in the container 
> runs as. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org

Reply via email to