[jira] [Updated] (HBASE-19164) Avoid UUID.randomUUID in tests

["Guanghao Zhang (JIRA)" <ji...@apache.org>]

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

Guanghao Zhang updated HBASE-19164:
-----------------------------------
    Fix Version/s: 2.2.0

> Avoid UUID.randomUUID in tests
> ------------------------------
>
>                 Key: HBASE-19164
>                 URL: https://issues.apache.org/jira/browse/HBASE-19164
>             Project: HBase
>          Issue Type: Improvement
>          Components: test
>            Reporter: Mike Drob
>            Assignee: Sahil Aggarwal
>            Priority: Major
>              Labels: beginner
>             Fix For: 3.0.0, 2.1.0, 2.2.0
>
>         Attachments: HBASE-19164.master.001.patch, HBASE-19164.master.002.patch, HBASE-19164.master.003.patch, HBASE-19164.master.004.patch, HBASE-19164.master.005.patch, HBASE-19164.master.006.patch, HBASE-19164.master.007.patch
>
>
> We have a lot of places in our test code where we use {{UUID.randomUUID}} to generate table names or paths for uniqueness. Unfortunately, this uses up a good chunk of system entropy, since Sun chose that random UUID's should use the NativePRNGBlocking implementation.
> We don't need to block on entropy for random bits to pick a random table name in a test, so we can use something that doesn't strain the system too much - secure random can be a source of problems on some VM or containers.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)