[
https://issues.apache.org/jira/browse/HADOOP-3633?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12624669#action_12624669
]
Hudson commented on HADOOP-3633:
--------------------------------
Integrated in Hadoop-trunk #581 (See
[http://hudson.zones.apache.org/hudson/job/Hadoop-trunk/581/])
> 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
> Environment: 17.0 + H1979-H2159-H3442
> Reporter: Koji Noguchi
> Assignee: Konstantin Shvachko
> Priority: Blocker
> Fix For: 0.17.2
>
> Attachments: DataXceivr-017.patch, DataXceivr-018.patch,
> DataXceivr.patch, DataXceivr.patch, jstack-H3633.txt
>
>
> Observed dfsclients timing out to some datanodes.
> Datanode's '.out' file had
> {noformat}
> Exception in thread "[EMAIL PROTECTED]" 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.
