You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Chung En Lee (Jira)" <ji...@apache.org> on 2025/10/21 20:55:06 UTC
[jira] [Updated] (HDDS-225) Provide docker-compose files to check the scalability of OzoneManager
[ https://issues.apache.org/jira/browse/HDDS-225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chung En Lee updated HDDS-225:
------------------------------
Target Version/s: 2.2.0 (was: 1.2.0)
2.2.0 (was: 2.1.0)
<<Bulk update>>
Apache Ozone 2.1.0 release is in progress. I'm updating all unresolved jiras targeting 2.1.0 to retarget 2.2.0.
> Provide docker-compose files to check the scalability of OzoneManager
> ---------------------------------------------------------------------
>
> Key: HDDS-225
> URL: https://issues.apache.org/jira/browse/HDDS-225
> Project: Apache Ozone
> Issue Type: Improvement
> Reporter: Marton Elek
> Priority: Major
> Attachments: HDDS-225.001.patch
>
>
> I open this jira to start a discussion. The main question: how can we prove the scalability of KSM with minimal effort?
> 1. The goal is to prove that KSM could handle 1-10 billion of keys without any problem.
> 2. 10 000 000 000 * 10 kbyte object = 10 Terrabyte space. But we need to test only the KSM part.
> 3. With a low level data generator we can generate the volumes/buckets/keys directly to the ksm.db (rocksdb). We can fake the block allocation and use exactly the same containerid/localid for all the keys. With this method we can test the read/list methods without any problems (all of the keys could be downloaded.
> 4. With this storage optimization we can test 10 billion keys locally with a specific docker-compose setup where the local db-s are mounted from the local directory
> 5. The data could be generated (takes some time) or could be uploaded after a generation
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org