@@ -35,6 +35,11 @@ You can learn how to:
35
35
- [ Reindex with an ingest pipeline] ( #reindex-with-an-ingest-pipeline )
36
36
- [ Reindex from remote] ( #reindex-from-remote )
37
37
38
+ ** Troubleshooting**
39
+ - [ Monitor reindex tasks] ( #monitor-reindex-tasks )
40
+ - [ Diagnose node failures] ( #diagnose-node-failures )
41
+ - [ Version conflicts] ( #version-conflicts )
42
+
38
43
## Basic reindexing example
39
44
40
45
Use the Reindex API to copy all documents from one index to another.
@@ -731,4 +736,50 @@ POST _reindex
731
736
Reindex from remote supports configurable SSL settings.
732
737
These must be specified in the `elasticsearch.yml` file, with the exception of the secure settings, which you add in the {{es}} keystore.
733
738
It is not possible to configure SSL in the body of the reindex API request.
734
- Refer to [Reindex settings](/reference/elasticsearch/configuration-reference/index-management-settings.md#reindex-settings).
739
+ Refer to [Reindex settings](/reference/elasticsearch/configuration-reference/index-management-settings.md#reindex-settings).
740
+
741
+ # # Monitor reindex tasks [monitor-reindex-tasks]
742
+
743
+ When run asynchronously with `wait_for_completion=false`, a reindex task can be monitored with the task management API :
744
+ ` ` ` console
745
+ GET _tasks/r1A2WoRbTwKZ516z6NEs5A:36619
746
+ ` ` `
747
+ % TEST[catch:missing]
748
+
749
+ To view all currently running reindex tasks :
750
+ ` ` ` console
751
+ GET _tasks?actions=*reindex
752
+ ` ` `
753
+
754
+ You can also cancel a running reindex task :
755
+ ` ` ` console
756
+ POST _tasks/r1A2WoRbTwKZ516z6NEs5A:36619/_cancel
757
+ ` ` `
758
+
759
+ # # Diagnose node failures [diagnose-node-failures]
760
+
761
+ Node crashes can sometimes be caused by insufficient disk space. To check disk allocation across your cluster :
762
+ ` ` ` console
763
+ GET _cat/allocation?v
764
+ ` ` `
765
+
766
+ # # Version conflicts [version-conflicts]
767
+
768
+ By default, version conflicts abort the reindexing process.
769
+ To continue reindexing in the case of conflicts, set `conflicts` to `proceed`.
770
+ This may be necessary when retrying a failed reindex operation, as the destination index could be left in a partial state.
771
+
772
+ ` ` ` console
773
+ POST _reindex
774
+ {
775
+ "source": {
776
+ "index": "my-index-000001"
777
+ },
778
+ "dest": {
779
+ "index": "my-new-index-000001",
780
+ "op_type": "create"
781
+ },
782
+ "conflicts": "proceed"
783
+ }
784
+ ` ` `
785
+ % TEST[setup:my_index]
0 commit comments