[
https://issues.apache.org/jira/browse/HADOOP-3348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12594648#action_12594648
]
lohit vijayarenu commented on HADOOP-3348:
------------------------------------------
Christophe, thanks for the pointer. Yes, on my LINUX machine, while running
this program I do see that /proc/sys/kernel/random/entropy_avail returns 0.
After digging a bit I came to know that, when this happens any readers of
/dev/random hang, which seems to be the case right now. Is it good idea to
make an assumption that this works on a system we are trying to bring up our
datanodes? Are there disadvantages to using Random.nextInt(Integer.MAX_VALUE);
> TestUrlStreamHandler hangs on LINUX
> -----------------------------------
>
> Key: HADOOP-3348
> URL: https://issues.apache.org/jira/browse/HADOOP-3348
> Project: Hadoop Core
> Issue Type: Bug
> Components: fs
> Affects Versions: 0.18.0
> Environment: LINUX 2.6.9
> Reporter: lohit vijayarenu
> Attachments: Datanode_jstack.txt
>
>
> TestUrlStreamHandler sets setURLStreamHandlerFactory as
> {noformat}
> FsUrlStreamHandlerFactory factory =
> new org.apache.hadoop.fs.FsUrlStreamHandlerFactory();
> java.net.URL.setURLStreamHandlerFactory(factory);
> {noformat}
> After this, MiniDFSCluster seems to hang while Datanodes tries to register in
> setNewStorageID, specifically at
> {noformat}
> rand = SecureRandom.getInstance("SHA1PRNG").nextInt(Integer.MAX_VALUE);
> {noformat}
> jstack output shows that the main thread is stuck in
> RawLocalFileSystem$LocalFSFileInputStream.read
> (Attaching the jstack)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
