[
https://issues.apache.org/jira/browse/HDDS-14447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Andika updated HDDS-14447:
-------------------------------
Description:
Currently OmMetadataGenerator only creates a single client which are shared by
all the threads. This is not suitable to test OM follower read since a single
client will only stick with a single OM most of the time. We want the more
clients so that the client workloads will be spread out to all the OM nodes.
Also we can support an option to allow clients to initially only connect to OM
followers.
We can specify the number of clients needed. If the clients are more than the
number of threads, we will bound it to the number of threads. Otherwise, we
will create N number of clients and each thread with index i can use i % N
client.
The default number of clients is 1 to preserve compatibility.
was:
Currently OmMetadataGenerator only creates a single client which are shared by
all the threads. This is not suitable to test OM follower read since a single
client will only stick with a single OM most of the time. We want the more
clients so that the client workloads will be spread out to all the OM nodes.
We can specify the number of clients needed. If the clients are more than the
number of threads, we will bound it to the number of threads. Otherwise, we
will create N number of clients and each thread with index i can use i % N
client.
The default number of clients is 1 to preserve compatibility.
> Support multiple clients in OmMetadataGenerator
> -----------------------------------------------
>
> Key: HDDS-14447
> URL: https://issues.apache.org/jira/browse/HDDS-14447
> Project: Apache Ozone
> Issue Type: Sub-task
> Reporter: Ivan Andika
> Assignee: Ivan Andika
> Priority: Major
>
> Currently OmMetadataGenerator only creates a single client which are shared
> by all the threads. This is not suitable to test OM follower read since a
> single client will only stick with a single OM most of the time. We want the
> more clients so that the client workloads will be spread out to all the OM
> nodes. Also we can support an option to allow clients to initially only
> connect to OM followers.
> We can specify the number of clients needed. If the clients are more than the
> number of threads, we will bound it to the number of threads. Otherwise, we
> will create N number of clients and each thread with index i can use i % N
> client.
> The default number of clients is 1 to preserve compatibility.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
