[Remote Store] Handle backward compatibility for primary term validation action #5635
Labels
enhancement
Enhancement or improvement to existing feature or request
Storage:Durability
Issues and PRs related to the durability framework
v2.8.0
'Issues and PRs related to version v2.8.0'
Is your feature request related to a problem? Please describe.
In Opensearch 2.5, we have a separate action for performing primary term validation which is used for remote backed indices with remote translog enabled. We need to validate if clusterService.state().getNodes().getMinNodeVersion() of all nodes is greater than this version to ensure remote translog works. Since this can break during mixed versions rolling upgrades. If there is a mixed cluster with let's say older version and 2.5, then a primary on 2.5 will send requests to replicas on older version which can fail to understand this. However, since this is an experimental feature, We can handle this when removing the experimental feature flag.
Refer - #5616 & #5616 for more context.
Describe the solution you'd like
We would need to handle the min version check for to be able to create a remote-backed index before a major release.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: