Raft read barrier API is not a part of 2024.2 #4183
Comments
Michal-Leszczynski
added a commit
that referenced
this issue
Dec 19, 2024
Michal-Leszczynski
added a commit
that referenced
this issue
Dec 20, 2024
It turns out that Scylla 2024.2 does not expose this API. For now, it's not know which enterprise release will contain it. Fixes #4183
Michal-Leszczynski
added a commit
that referenced
this issue
Dec 20, 2024
It turns out that Scylla 2024.2 does not expose this API. For now, it's not know which enterprise release will contain it, so we need to fall back to the CQL workaround. Fixes #4183
|
Did you ask for a backport of scylladb/scylladb#19597 ? Perhaps it's easily doable. |
|
I wouldn't say that we need to backport it, as we have another way issuing raft read barrier that was used before. The general problem is that the only way for SM to check if given Scylla version supports some feature is by version checking. This sometimes gets messy with temporary versions used for testing (e.g. build from master which identifies with 2024.2.X-Y-Z version contains given feature, but the actual 2024.2.0 release does not). In the context of this issue, for some reason I thought that 2024.2 is based on 6.1 (which contains the new API), but it is based on 6.0 (which does not include it). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Recently #3932 was fixed. It assumed that the raft read barrier API will be a part of the 2024.2 release, but that's not the case.
When running SCT against Scylla 2024.2 we get HTTP 404 when querying non-existence Scylla API:
Unfortunately, because of scylladb/scylladb#16424, we need rely on version checks, so there is no way around it.
We could try to make empirically check if Scylla exposes given API endpoint by checking for HTTP 404 status code, but this probably wouldn't be really robust.
The text was updated successfully, but these errors were encountered: