You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2022/04/02 00:43:00 UTC
[jira] [Updated] (HDDS-6209) EC: [Forward compatibility issue] New client to older server could fail due to the unavailability for client default replication config
[ https://issues.apache.org/jira/browse/HDDS-6209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated HDDS-6209:
---------------------------------
Labels: pull-request-available (was: )
> EC: [Forward compatibility issue] New client to older server could fail due to the unavailability for client default replication config
> ---------------------------------------------------------------------------------------------------------------------------------------
>
> Key: HDDS-6209
> URL: https://issues.apache.org/jira/browse/HDDS-6209
> Project: Apache Ozone
> Issue Type: Sub-task
> Components: OM, Ozone Client
> Affects Versions: EC-Branch
> Reporter: Uma Maheswara Rao G
> Assignee: István Fajth
> Priority: Major
> Labels: pull-request-available
>
> In EC branch code, we removed the client side default configurations and moved the default configurations to server side.
> In case of client upgraded with newer client, but server are still old, will not understand the situation of client config unavailability as older server always expects the replication configs from client.
>
> I think as part of S3G, there are some implementations to handle the version incompatibilities. example OM handshaking it's version to client and client maintaining it's current version could help to solve the issue.
>
> CC: [~erose] [~kerneltime]
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org