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

Posted to common-issues@hadoop.apache.org by "Kihwal Lee (JIRA)" <ji...@apache.org> on 2014/05/16 13:01:43 UTC

[jira] [Resolved] (HADOOP-10588) Workaround for jetty6 acceptor startup issue

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

Kihwal Lee resolved HADOOP-10588.
---------------------------------

       Resolution: Fixed
    Fix Version/s: 2.5.0
                   0.23.11
     Hadoop Flags: Reviewed

Thanks for the reviews, Sangjin and Jon. I've committed this to branch-0.23 and branch-2.

> Workaround for jetty6 acceptor startup issue
> --------------------------------------------
>
>                 Key: HADOOP-10588
>                 URL: https://issues.apache.org/jira/browse/HADOOP-10588
>             Project: Hadoop Common
>          Issue Type: Bug
>            Reporter: Kihwal Lee
>            Assignee: Kihwal Lee
>             Fix For: 0.23.11, 2.5.0
>
>         Attachments: selector.patch, selector23.patch
>
>
> When a cluster is restarted, jetty is not functioning for a small percentage of datanodes, requiring restart of those datanodes.  This is caused by JETTY-1316.
> We've tried overriding isRunning() and retrying on super.isRunning() returning false, as the reporter of JETTY-1316 mentioned in the description.  It looks like the code was actually exercised (i.e. the issue was caused by this jetty bug)  and the acceptor was working fine after retry.
> Since we will probably move to a later version of jetty after branch-3 is cut, we can put this workaround in branch-2 only.



--
This message was sent by Atlassian JIRA
(v6.2#6252)