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 "Wei-Chiu Chuang (JIRA)" <ji...@apache.org> on 2016/08/19 16:44:20 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=15428427#comment-15428427 ]
Wei-Chiu Chuang commented on HADOOP-10588:
------------------------------------------
Two years after this was committed, The Jetty in Hadoop 3 is still not upgraded. I think that either we bump Jetty's version (unlikely) or we cherry pick this fix to trunk.
> 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.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org