You are viewing a plain text version of this content. The canonical link for it is here.

Posted to mapreduce-issues@hadoop.apache.org by "Jason Lowe (JIRA)" <ji...@apache.org> on 2015/10/21 16:19:27 UTC

[jira] [Moved] (MAPREDUCE-6518) Set SO_KEEPALIVE on NM servers

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

Jason Lowe moved YARN-4052 to MAPREDUCE-6518:
---------------------------------------------

    Affects Version/s:     (was: 2.7.1)
                       2.7.1
          Component/s:     (was: nodemanager)
                       nodemanager
                       mrv2
                  Key: MAPREDUCE-6518  (was: YARN-4052)
              Project: Hadoop Map/Reduce  (was: Hadoop YARN)

> Set SO_KEEPALIVE on NM servers
> ------------------------------
>
>                 Key: MAPREDUCE-6518
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-6518
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv2, nodemanager
>    Affects Versions: 2.7.1
>            Reporter: Nathan Roberts
>            Assignee: Chang Li
>         Attachments: YARN-4052.2.patch, YARN-4052.3.patch, YARN-4052.patch
>
>
> Shuffle handler does not set SO_KEEPALIVE so we've seen cases where FDs/sockets get stuck in ESTABLISHED state indefinitely because the server did not see the client leave (network cut or otherwise). 



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