SDK compatibility for cluster updates #40

New issue

Open

opened 2023-03-23 13:38:32 +00:00 by alexvanin · 2 comments

alexvanin commented

2023-03-23 13:38:32 +00:00

Owner

We want to support rolling updates for FrostFS clusters. This means that FrostFS network may contain some new and some old versions of FrostFS node and gateways. So there are two requirements:

New versions should not use new protocol features when talking to old nodes.
New versions should not use new protocol features while consensus nodes are old (e.g. IR can't approve new __SYSTEM__* attribute).

So basically SDK client / pool should consider its own version, remote node version and network map (consensus) version and use min version to update request (for example replace new attribute with legacy attribute in container body).

Let's start doing this with all incoming protocol changes besides TrueCloudLab/frostfs-api#14.

Consider cluster of FrostFS nodes. From time to time we update protocol version and some update may be compatible in terms of protobuf definitions but not compatible in terms of value interpretation (see `__SYSTEM__` attribute in https://git.frostfs.info/TrueCloudLab/frostfs-api/issues/14). We want to support rolling updates for FrostFS clusters. This means that FrostFS network may contain some new and some old versions of FrostFS node and gateways. So there are two requirements: 1. New versions **should not** use new protocol features when talking to old nodes. 2. New versions **should not** use new protocol features while consensus nodes are old (e.g. IR can't approve new `__SYSTEM__*` attribute). So basically SDK client / pool should consider its own version, remote node version and network map (consensus) version and use _min version_ to update request (for example replace new attribute with legacy attribute in container body). Let's start doing this with all incoming protocol changes besides https://git.frostfs.info/TrueCloudLab/frostfs-api/issues/14.

alexvanin referenced this issue from TrueCloudLab/frostfs-s3-gw

2023-03-23 13:43:51 +00:00

Init S3 Credentials failed #67

alexvanin referenced this issue from TrueCloudLab/frostfs-http-gw

2023-03-23 13:44:25 +00:00

[#22] Update system attributes #22

fyrchik commented

2023-05-02 08:00:33 +00:00

Owner

Do you suggest doing something now is it a documentation change?

alexvanin commented

2023-05-02 11:42:51 +00:00

Author

Owner

@fyrchik I would like to discuss and document the version sync approach between peers in this issue.

This issue highlights an interesting case, when protocol version negotiation should consider inner ring (network map) version too, e.g. for new 'well-known' attributes.

@fyrchik I would like to discuss and document the version sync approach between peers in this issue. This issue highlights an interesting case, when protocol version negotiation should consider inner ring (network map) version too, e.g. for new 'well-known' attributes.