You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Koji Noguchi (JIRA)" <ji...@apache.org> on 2008/06/25 01:45:44 UTC
[jira] Updated: (HADOOP-3633) Uncaught exception in
DataXceiveServer
[ https://issues.apache.org/jira/browse/HADOOP-3633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Koji Noguchi updated HADOOP-3633:
---------------------------------
Attachment: jstack-H3633.txt
Datanode's stack trace.
It doesn't show DataXceiveServer running
> Uncaught exception in DataXceiveServer
> --------------------------------------
>
> Key: HADOOP-3633
> URL: https://issues.apache.org/jira/browse/HADOOP-3633
> Project: Hadoop Core
> Issue Type: Bug
> Components: dfs
> Affects Versions: 0.17.0
> Reporter: Koji Noguchi
> Attachments: jstack-H3633.txt
>
>
> Observed dfsclients timing out to some datanodes.
> Datanode's '.out' file had
> {noformat}
> Exception in thread "org.apache.hadoop.dfs.DataNode$DataXceiveServer@82d37" java.lang.OutOfMemoryError: unable to create new native thread
> at java.lang.Thread.start0(Native Method)
> at java.lang.Thread.start(Thread.java:597)
> at org.apache.hadoop.dfs.DataNode$DataXceiveServer.run(DataNode.java:906)
> at java.lang.Thread.run(Thread.java:619)
> {noformat}
> Datanode was still running but not much activity besides verification.
> Jstack showed no DataXceiveServer running.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.