Versions (relevant - OpenSearch/Dashboard/Server OS/Browser):
Opensearch 1.3 to 2.x migration
Describe the issue:
I need to plan a customer data upgrade and would like
some experience feedback about upgrade times for tens or hundreds of GB of index data (depending on the platform).
All my indices were created in 1.3, so Lucene-version-compatible as I understand the documentation ; but if you can provide rough duration you encountered with associated hypothesis (number/size of indices, platform resources) it would be helpful
Rolling Upgrade duration would just be the time for shard copy during the migration, for a cluster handling low hundreds of GBs, i would expect shard reallocation throughput to be at least 20MBps per node (this is configurable with cluster settings) and say there are at least 3 nodes in the cluster, this would give 2 hours for the reallocation of 500GB.
If you want a migration path here that would support rollback, you can look at Migration Assistant which can support you migrating to a new cluster, even multi hop migrations (e.g. 1.3 → 3.x) while automatically reindexing the data to the current lucene version.