[
https://issues.apache.org/jira/browse/HADOOP-9857?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13735320#comment-13735320
]
Arpit Agarwal commented on HADOOP-9857:
---------------------------------------
{quote}
the JVM tries to do an exact string match on "file:/dev/urandom" in logic for
selecting the native entropy provider on Windows.
{quote}
Nice find! Would you consider documenting it in the pom.xml where you make this
setting for Windows? It is hard to guess why we use a non-existent device on
Windows.
Verified that {{TestProtoBufRpc}} and {{TestDoAsEffectiveUser}} are fixed by
the patch. They used to fail.
Interestingly {{TestDoAsEffectiveUser}} fails with JDK7 with an unrelated
issue. I will file a separate Jira for that.
> Tests block and sometimes timeout on Windows due to invalid entropy source.
> ---------------------------------------------------------------------------
>
> Key: HADOOP-9857
> URL: https://issues.apache.org/jira/browse/HADOOP-9857
> Project: Hadoop Common
> Issue Type: Bug
> Components: build, test
> Affects Versions: 3.0.0, 2.1.1-beta
> Reporter: Chris Nauroth
> Assignee: Chris Nauroth
> Attachments: HADOOP-9857.1.patch
>
>
> Tests are configured to set the entropy source to {{file:///dev/urandom}} to
> prevent blocking on machines with low entropy. We've observed that on
> Windows, this will cause tests to block for 5 seconds trying to access this
> non-existent path the first time the process does something that needs
> entropy, such as using a {{SecureRandom}} or creating a {{UUID}}. This can
> cause tests to fail due to timeouts. In addition to the initial 5-second
> blocking, this causes the JVM to fall back to a slower, non-native seed
> generation implementation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
