[
https://issues.apache.org/jira/browse/HDDS-8273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Attila Doroszlai updated HDDS-8273:
-----------------------------------
Fix Version/s: 1.4.0
Resolution: Implemented
Status: Resolved (was: Patch Available)
> EC: Validate replication config at server-side
> ----------------------------------------------
>
> Key: HDDS-8273
> URL: https://issues.apache.org/jira/browse/HDDS-8273
> Project: Apache Ozone
> Issue Type: Sub-task
> Components: Ozone Manager
> Reporter: Stephen O'Donnell
> Assignee: Attila Doroszlai
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.4.0
>
>
> Replication config validation is all client side. Looking for usages of
> {{ReplicationConfigValidator.validate()}}, it is used when the config is
> parsed from the string form, and then it is used in {{RPCClient.createKey()}}
> to validate the RepConfig object, but it does not seem to be validated server
> side.
> I think we should add a validation in OM's createKey to enforce the rule at
> the server side, as it would be possible for a user to change the client side
> config and then submit keys with any repConfig without the admin being aware
> of it.
> At least if we have a rule at the server side, someone has to make a decision
> to adjust the rule and restart OM for it to take effect.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
