[
https://issues.apache.org/jira/browse/HDDS-15602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Andika updated HDDS-15602:
-------------------------------
Description:
We found that the CPU time of createPipelineForRead is mostly fonr SecureRandom
that looks like requiring a static monitor lock. I don't think it is required
to use SecureRandom. Since the SecureRandom is static, it also contends with
all other UUID generation.
!image-2026-06-18-17-44-58-985.png|width=855,height=678!
was:
We found that the CPU usage of createPipelineForRead is mostly for SecureRandom
that looks like requiring a monitor lock. I don't think it is required to use
SecureRandom.
!image-2026-06-18-17-44-58-985.png|width=855,height=678!
> PipelineId randomId does not need to use secure random
> ------------------------------------------------------
>
> Key: HDDS-15602
> URL: https://issues.apache.org/jira/browse/HDDS-15602
> Project: Apache Ozone
> Issue Type: Improvement
> Reporter: Ivan Andika
> Assignee: Ivan Andika
> Priority: Major
> Attachments: image-2026-06-18-17-44-58-985.png
>
>
> We found that the CPU time of createPipelineForRead is mostly fonr
> SecureRandom that looks like requiring a static monitor lock. I don't think
> it is required to use SecureRandom. Since the SecureRandom is static, it also
> contends with all other UUID generation.
> !image-2026-06-18-17-44-58-985.png|width=855,height=678!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
