Paul Tomblin wrote:
On Sat, Nov 28, 2009 at 5:48 PM, Andrzej Bialecki <a...@getopt.org> wrote:
Paul Tomblin wrote:
-bash-3.2$ jstack -F 32507
Attaching to process ID 32507, please wait...
Hm, I can't see anything obviously wrong with that thread dump. What's the
CPU and swap usage, and loadavg?
The process is using a lot of CPU. loadavg is up over 5.
top - 15:12:19 up 22 days, 4:06, 2 users, load average: 5.01, 5.00, 4.93
Tasks: 48 total, 2 running, 45 sleeping, 0 stopped, 1 zombie
Cpu(s): 1.0% us, 99.0% sy, 0.0% ni, 0.0% id, 0.0% wa, 0.0% hi, 0.0% si
Mem: 3170584k total, 2231700k used, 938884k free, 0k buffers
Swap: 0k total, 0k used, 0k free, 0k cached
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
32507 discover 16 0 1163m 974m 8604 S 394.7 31.5 719:40.71 java
Actually, the memory is a real annoyance - the hosting company doesn't
give me any swap, so when hadoop does a fork/exec just to do a
"whoami", I have to leave as much memory free as the crawl reserves
with -Xmx for itself.
Hm, the curious thing here is that the java process is sleeping, and 99%
of cpu is in "system" time ... usually this would indicate swapping, but
since there is no swap in your setup I'm stumped. Still, this may be
related to the weird memory/swap setup on that machine - try decreasing
the heap size and see what happens.
--
Best regards,
Andrzej Bialecki <><
___. ___ ___ ___ _ _ __________________________________
[__ || __|__/|__||\/| Information Retrieval, Semantic Web
___|||__|| \| || | Embedded Unix, System Integration
http://www.sigram.com Contact: info at sigram dot com
