Issue: From 7.12 and above, ES has introduced UUIDs as identifiers for repositories instead on names to better there solutions like ILM, SLM etc this has also introduced things like writer uuid's on shard which is breaking the compatibility with OpenSearch which is a fork on ES 7.10. This is clearly called out on many blogs where data from ES 7.12 and above can not be migrated to OpenSearch at this point in time. Also Elasticsearch themselves doesn't support the data migration on lower versions on the cluster which in our case is also true, i.e from 7.16 to 7.10.
Explorations: The below explorations were tried on ES 7.10 and OpenSearch 1.0/1.1
We tried unpacking the snapshots and explored on the options to enable the backward compatibility and was successful in syncing the snapshots, viewing the list of snapshots available and restoring the snapshots but failed in shard allocation.
To Reproduce
Steps to reproduce the behavior:
Install '...'
Run '....'
Scroll down to '....'
See error
Expected behavior
A clear and concise description of what you expected to happen.
Configuration (please complete the following information):
ODFE/Kibana version [e.g. 1.7.0, 1.8.0]
Distribution [e.g. RPM, DEB, TAR, etc]
Host Machine [e.g: Centos7, MacOS]
Relevant information
Please include any relevant log snippets or files here.
Describe the bug
Issue: From 7.12 and above, ES has introduced UUIDs as identifiers for repositories instead on names to better there solutions like ILM, SLM etc this has also introduced things like writer uuid's on shard which is breaking the compatibility with OpenSearch which is a fork on ES 7.10. This is clearly called out on many blogs where data from ES 7.12 and above can not be migrated to OpenSearch at this point in time. Also Elasticsearch themselves doesn't support the data migration on lower versions on the cluster which in our case is also true, i.e from 7.16 to 7.10.
Explorations: The below explorations were tried on ES 7.10 and OpenSearch 1.0/1.1
We tried unpacking the snapshots and explored on the options to enable the backward compatibility and was successful in syncing the snapshots, viewing the list of snapshots available and restoring the snapshots but failed in shard allocation.
To Reproduce Steps to reproduce the behavior:
Expected behavior A clear and concise description of what you expected to happen.
Configuration (please complete the following information):
Relevant information Please include any relevant log snippets or files here.