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

Ted Yu updated KYLIN-3317:
--------------------------
    Description: 
Currently UUID.randomUUID is called in various places in the code base.
* It is non-deterministic.
* It uses a single secure random for UUID generation. This uses a single JVM 
wide lock, and this can lead to lock contention and other performance problems.

We should move to something that is deterministic by using seeded PRNGs
{code}
new UUID(ThreadLocalRandom.current().nextLong(), 
ThreadLocalRandom.current().nextLong())
{code}

  was:
Currently UUID.randomUUID is called in various places in the code base.

* It is non-deterministic.
* It uses a single secure random for UUID generation. This uses a single JVM 
wide lock, and this can lead to lock contention and other performance problems.

We should move to something that is deterministic by using seeded PRNGs
{code}
new UUID(ThreadLocalRandom.current().nextLong(), 
ThreadLocalRandom.current().nextLong())
{code}


> Replace UUID.randomUUID with deterministic PRNG
> -----------------------------------------------
>
>                 Key: KYLIN-3317
>                 URL: https://issues.apache.org/jira/browse/KYLIN-3317
>             Project: Kylin
>          Issue Type: Task
>          Components: Security
>            Reporter: Ted Yu
>            Assignee: jiatao.tao
>            Priority: Major
>             Fix For: v2.5.0
>
>
> Currently UUID.randomUUID is called in various places in the code base.
> * It is non-deterministic.
> * It uses a single secure random for UUID generation. This uses a single JVM 
> wide lock, and this can lead to lock contention and other performance 
> problems.
> We should move to something that is deterministic by using seeded PRNGs
> {code}
> new UUID(ThreadLocalRandom.current().nextLong(), 
> ThreadLocalRandom.current().nextLong())
> {code}



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

Reply via email to