ce441bdc32
* Instead of cloning, reindex legacy index * Reindex for every v2 migration * Use _reindex?require_alias=true and a write block toggle to prevent lost deletes * Use a ..._reindex_in_progress alias so that waiting for and preventing other reindex operations is idempotent The first version of the reindex block had only the instance which was able to mark the migration as complete set and remove the write block. This means other instances couldn't know if any reindex operaitons were in progress if the migration was already marked as complete. It also meant that a failure in this critical step could result in a permanent write block. * Revert "Use a ..._reindex_in_progress alias so that waiting for and preventing other reindex operations is idempotent" This reverts commit |
||
|---|---|---|
| .. | ||
| .gitkeep | ||
| 0001_lifecycle_setup.md | ||
| 0002_encrypted_attributes.md | ||
| 0003_handler_interface.md | ||
| 0004_application_service_mounting.md | ||
| 0005_route_handler.md | ||
| 0006_management_section_service.md | ||
| 0007_lifecycle_unblocked.md | ||
| 0008_pulse.md | ||
| 0010_service_status.md | ||
| 0011_global_search.md | ||
| 0011_reporting_as_an_api.md | ||
| 0012_encryption_key_rotation.md | ||
| 0013_saved_object_migrations.md | ||
| 0013_search_sessions.md | ||
| 0014_api_documentation.md | ||