[
https://issues.apache.org/jira/browse/HDDS-225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prashant Pogde updated HDDS-225:
--------------------------------
Target Version/s: 1.2.0
I am managing the 1.1.0 release and we currently have more than 600 issues
targeted for 1.1.0. I am moving the target field to 1.2.0.
If you are actively working on this jira and believe this should be targeted to
1.1.0 release, Please change the target field back to 1.1.0 before Feb 05,
2021.
> Provide docker-compose files to check the scalability of OzoneManager
> ---------------------------------------------------------------------
>
> Key: HDDS-225
> URL: https://issues.apache.org/jira/browse/HDDS-225
> Project: Hadoop Distributed Data Store
> Issue Type: Improvement
> Reporter: Marton Elek
> Assignee: Bharat Viswanadham
> 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.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
