[
https://issues.apache.org/jira/browse/HBASE-19164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16241483#comment-16241483
]
Sahil Aggarwal edited comment on HBASE-19164 at 11/7/17 4:53 AM:
-----------------------------------------------------------------
I see multiple tests using
{code:java}
UUID.randomUUID()
{code}
, do we just need to replace it with
{code:java}
new UUID(ThreadLocalRandom.current().nextLong(),
ThreadLocalRandom.current().nextLong()
{code}
)
was (Author: awked06):
I see multiple tests using ```UUID.randomUUID()```, do we just need to replace
it with ```new UUID(ThreadLocalRandom.current().nextLong(),
ThreadLocalRandom.current().nextLong())```
> 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
> Labels: beginner
>
> 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
(v6.4.14#64029)
