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 "Sangjin Lee (JIRA)" <ji...@apache.org> on 2014/05/11 00:14:55 UTC

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

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

Sangjin Lee commented on HADOOP-10588:
--------------------------------------

LGTM. We also run into this issue sporadically.

> 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
>         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)