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 "Todd Lipcon (JIRA)" <ji...@apache.org> on 2011/06/03 20:31:48 UTC
[jira] [Commented] (MAPREDUCE-2386) TT jetty server stuck in tight
loop around epoll_wait
[ https://issues.apache.org/jira/browse/MAPREDUCE-2386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13043950#comment-13043950 ]
Todd Lipcon commented on MAPREDUCE-2386:
----------------------------------------
Konstantin: downgrading to Jetty 6.1.14 seems to be an effective workaround. Unfortunately it opens you up to some XSS security holes, but in some clusters that might be preferable :)
> TT jetty server stuck in tight loop around epoll_wait
> -----------------------------------------------------
>
> Key: MAPREDUCE-2386
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2386
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: tasktracker
> Affects Versions: 0.23.0
> Environment: RHEL 6.0 "Santiago"
> Reporter: Todd Lipcon
>
> In some load testing, I got a TaskTracker into a state where its Jetty server is in a tight loop calling epoll_wait, which is returning EINVAL:
> [pid 19573] epoll_wait(157, 40829000, 8192, 0) = -1 EINVAL (Invalid argument)
> It's not responding to any HTTP connections - connections are accepted and then just hang.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira