You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@kylin.apache.org by "Ted Yu (JIRA)" <ji...@apache.org> on 2018/04/05 22:20:00 UTC

[jira] [Updated] (KYLIN-3317) Replace UUID.randomUUID with deterministic PRNG

     [ 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

  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


> Replace UUID.randomUUID with deterministic PRNG
> -----------------------------------------------
>
>                 Key: KYLIN-3317
>                 URL: https://issues.apache.org/jira/browse/KYLIN-3317
>             Project: Kylin
>          Issue Type: Task
>            Reporter: Ted Yu
>            Priority: Major
>
> 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



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