[
https://issues.apache.org/jira/browse/HDDS-6416?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kaijie Chen updated HDDS-6416:
------------------------------
Description:
Currently, the priority of replication config in ozone fs is: bucket EC >
createFile() parameter > client > bucket others > cluster.
And it also requires polling bucket level replication config from the client.
It will be nice if we could find a way to make fs replication priority same as
key space.
Which is: client > bucket > cluster. And thus remove the need of polling.
was:
Currently, createFile() will always send a replicationConfig to OM.
So OM will never have a chance to fallback to the cluster-level config.
And there is also a hacky polling to get bucket level config at the client side.
In this JIRA, we are going to improve the replicationConfig logic in createFile.
If client side config is null, let's just pass null to let the server decide.
> EC: Support cluster-level EC config in Ozone FS
> -----------------------------------------------
>
> Key: HDDS-6416
> URL: https://issues.apache.org/jira/browse/HDDS-6416
> Project: Apache Ozone
> Issue Type: Sub-task
> Reporter: Kaijie Chen
> Assignee: Kaijie Chen
> Priority: Major
>
> Currently, the priority of replication config in ozone fs is: bucket EC >
> createFile() parameter > client > bucket others > cluster.
> And it also requires polling bucket level replication config from the client.
>
> It will be nice if we could find a way to make fs replication priority same
> as key space.
> Which is: client > bucket > cluster. And thus remove the need of polling.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
