hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suresh Srinivas (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-6057) DomainSocketWatcher.watcherThread should be marked as daemon thread
Date Wed, 05 Mar 2014 23:32:44 GMT

    [ https://issues.apache.org/jira/browse/HDFS-6057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13921622#comment-13921622
] 

Suresh Srinivas commented on HDFS-6057:
---------------------------------------

[~cmccabe], some of the recent changes related to short circuits related work have caused
few bugs. This has impacted some of the testing that we are doing in terms of stabilization.
I have few questions:
# Does this need to go into release 2.4? I think currently 2.4 should either get changes related
to previous feature we talked about, blocker bugs or any code changes (that involves refactoring)
that makes future code merges harder.
# Can you please share the plan of what other work you are planning that will make it into
2.4?

> DomainSocketWatcher.watcherThread should be marked as daemon thread
> -------------------------------------------------------------------
>
>                 Key: HDFS-6057
>                 URL: https://issues.apache.org/jira/browse/HDFS-6057
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: hdfs-client
>    Affects Versions: 2.4.0
>            Reporter: Eric Sirianni
>            Assignee: Ted Yu
>            Priority: Blocker
>         Attachments: hdfs-6057-v1.txt
>
>
> Running the tip of {{branch-2.4}}, I'm observing some zombie processes in my environment.
 jstack shows the following thread preventing the JVM from shutting down:
> {noformat}
> "Thread-3" prio=10 tid=0x00007f0a908a5800 nid=0x3ee9 runnable [0x00007f0a89471000]
>    java.lang.Thread.State: RUNNABLE
> 	at org.apache.hadoop.net.unix.DomainSocketWatcher.doPoll0(Native Method)
> 	at org.apache.hadoop.net.unix.DomainSocketWatcher.access$800(DomainSocketWatcher.java:52)
> 	at org.apache.hadoop.net.unix.DomainSocketWatcher$1.run(DomainSocketWatcher.java:455)
> 	at java.lang.Thread.run(Thread.java:679)
> {noformat}
> Marking the {{DomainSocketWatcher.watcherThread}} as a daemon thread would prevent this
situation.  Is there any reason it isn't classified as such?
> Also, tracing through the code, I don't see any code path where {{DomainSocketWatcher.close()}}
is invoked (though this would seem to be a larger issue -- maybe I'm missing something...).



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message