You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Elasticsearch main can't form a cluster with 8.19 because it thinks the changes associated with 127633 are back - but they are not. Instead 127639 and 127623 are.
I'm going to try and brain main into compatibility with 8.19 by modifying main only because I think that'll be less work. To do that, I'm taking the number claimed by 127633 and giving it to 127639. Then I'm adding support to main for 127623.
nik9000
added a commit
to nik9000/elasticsearch
that referenced
this issue
May 2, 2025
In elastic#127623 we backported elastic#127299 and added a backport transport version
for it - `ESQL_AGGREGATE_METRIC_DOUBLE_BLOCK_8_19` aka `8_841_0_24`.
This brings that version forwards to `main` and adds support for parsing
streams with that version.
In elastic#127639 we backported elastic#126401 and added a backport transport version
for it - `PINNED_RETRIEVER_8_19` aka `8_841_0_23`. This brings that
version forwards to `main` and adds support for parsing streams with
that versions.
In elastic#127633 we a claimed a backport transport version to backport elastic#127314 -
`INTRODUCE_FAILURES_LIFECYCLE_BACKPORT_8_19` aka `8_841_0_23`. That's
the same versions as `PINNED_RETRIEVER_8_19`. It's just that this one is
in `main` and `PINNED_RETRIEVER_8_19` is in `8.19`. To allow me to bring
`PINNED_RETRIEVER_8_19` for wards I've had to revert elastic#127633.
Closeselastic#127667
Description
Here's main:
Here's 8.19:
These aren't compatible with one another and
main
can't rolling upgrade from 8.19 at the moment.The text was updated successfully, but these errors were encountered: