Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
0.23.0, 1.0.3
-
None
-
None
-
RHEL 6.0 "Santiago"
Description
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.
Attachments
Issue Links
- is duplicated by
-
MAPREDUCE-2530 TaskTracker jetty stuck in a tight loop
- Resolved
-
MAPREDUCE-5949 Tasktracker's java threads hunging
- Resolved
- is related to
-
MAPREDUCE-1950 Jetty Acceptor can stuck TaskTracker forever
- Open
-
MAPREDUCE-2530 TaskTracker jetty stuck in a tight loop
- Resolved
- relates to
-
MAPREDUCE-2389 Spurious EOFExceptions reading SpillRecord index files
- Open
-
HADOOP-7191 BackUpNameNode is using 100% CPU and not accepting any requests.
- Resolved