hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Nauroth (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-9857) Tests block and sometimes timeout on Windows due to invalid entropy source.
Date Fri, 09 Aug 2013 22:20:48 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-9857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Chris Nauroth updated HADOOP-9857:

    Hadoop Flags: Reviewed

-1 tests included. The patch doesn't appear to include any new or modified tests.
Please justify why no new tests are needed for this patch.
Also please list what manual steps were performed to verify this patch.

There are no new tests required, because this patch fixes multiple existing tests on Windows.

Thanks for the review, Arpit.  I'll commit this.
> 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, HADOOP-9857.2.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

View raw message