[jira] [Updated] (HBASE-19164) Avoid UUID.randomUUID in tests
[ 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: (was: 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 > > 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)
[jira] [Updated] (HBASE-19164) Avoid UUID.randomUUID in tests
[ 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)
[jira] [Updated] (HBASE-19164) Avoid UUID.randomUUID in tests
[ https://issues.apache.org/jira/browse/HBASE-19164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Drob updated HBASE-19164: -- Resolution: Fixed Fix Version/s: 2.1.0 3.0.0 Status: Resolved (was: Patch Available) Pushed to branch-2.1+ (fyi [~Apache9]) Thanks for the patch [~awked06]! > 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 > > 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)
[jira] [Updated] (HBASE-19164) Avoid UUID.randomUUID in tests
[ https://issues.apache.org/jira/browse/HBASE-19164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sahil Aggarwal updated HBASE-19164: --- Attachment: HBASE-19164.master.007.patch > 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 > 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)
[jira] [Updated] (HBASE-19164) Avoid UUID.randomUUID in tests
[ https://issues.apache.org/jira/browse/HBASE-19164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sahil Aggarwal updated HBASE-19164: --- Attachment: HBASE-19164.master.006.patch > 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 > 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 > > > 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)
[jira] [Updated] (HBASE-19164) Avoid UUID.randomUUID in tests
[ https://issues.apache.org/jira/browse/HBASE-19164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sahil Aggarwal updated HBASE-19164: --- Attachment: HBASE-19164.master.005.patch > 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 > 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 > > > 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)
[jira] [Updated] (HBASE-19164) Avoid UUID.randomUUID in tests
[ https://issues.apache.org/jira/browse/HBASE-19164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sahil Aggarwal updated HBASE-19164: --- Attachment: HBASE-19164.master.004.patch > 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 > Attachments: HBASE-19164.master.001.patch, > HBASE-19164.master.002.patch, HBASE-19164.master.003.patch, > HBASE-19164.master.004.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)
[jira] [Updated] (HBASE-19164) Avoid UUID.randomUUID in tests
[ https://issues.apache.org/jira/browse/HBASE-19164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sahil Aggarwal updated HBASE-19164: --- Status: Open (was: Patch Available) > 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 > Labels: beginner > Attachments: HBASE-19164.master.001.patch, > HBASE-19164.master.002.patch, HBASE-19164.master.003.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 (v6.4.14#64029)
[jira] [Updated] (HBASE-19164) Avoid UUID.randomUUID in tests
[ https://issues.apache.org/jira/browse/HBASE-19164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sahil Aggarwal updated HBASE-19164: --- Status: Patch Available (was: Open) > 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 > Labels: beginner > Attachments: HBASE-19164.master.001.patch, > HBASE-19164.master.002.patch, HBASE-19164.master.003.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 (v6.4.14#64029)
[jira] [Updated] (HBASE-19164) Avoid UUID.randomUUID in tests
[ https://issues.apache.org/jira/browse/HBASE-19164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sahil Aggarwal updated HBASE-19164: --- Attachment: HBASE-19164.master.003.patch > 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 > Labels: beginner > Attachments: HBASE-19164.master.001.patch, > HBASE-19164.master.002.patch, HBASE-19164.master.003.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 (v6.4.14#64029)
[jira] [Updated] (HBASE-19164) Avoid UUID.randomUUID in tests
[ https://issues.apache.org/jira/browse/HBASE-19164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sahil Aggarwal updated HBASE-19164: --- Attachment: HBASE-19164.master.002.patch > 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 > Labels: beginner > Attachments: HBASE-19164.master.001.patch, > HBASE-19164.master.002.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 (v6.4.14#64029)
[jira] [Updated] (HBASE-19164) Avoid UUID.randomUUID in tests
[ https://issues.apache.org/jira/browse/HBASE-19164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sahil Aggarwal updated HBASE-19164: --- Status: Patch Available (was: Open) > 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 > Labels: beginner > Attachments: HBASE-19164.master.001.patch, > HBASE-19164.master.002.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 (v6.4.14#64029)
[jira] [Updated] (HBASE-19164) Avoid UUID.randomUUID in tests
[ https://issues.apache.org/jira/browse/HBASE-19164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sahil Aggarwal updated HBASE-19164: --- Attachment: HBASE-19164.master.001.patch > 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 > Labels: beginner > Attachments: HBASE-19164.master.001.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 (v6.4.14#64029)
[jira] [Updated] (HBASE-19164) Avoid UUID.randomUUID in tests
[ https://issues.apache.org/jira/browse/HBASE-19164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sean Busbey updated HBASE-19164: Issue Type: Improvement (was: Bug) > 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 >Priority: Major > 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)