@@ -183,12 +183,15 @@ need to be migrated or deleted, and upgrade the internal indices to the
183
183
+
184
184
You can also call the Elasticsearch migration APIs directly:
185
185
+
186
- `/_migration/assistance`:: Runs a series of checks on your cluster,
187
- nodes, and indices and returns a list of issues that need to be
188
- fixed before you can upgrade to {version}.
186
+ `/_xpack/migration/deprecations`:: Retrieves information about cluster-, node-,
187
+ and index-level settings that use deprecated features.
189
188
+
190
- `/_migration/upgrade`:: Upgrades the indices for the {watcher} and
191
- {security-features} to a single-type format compatible with Elasticsearch 6.x.
189
+ `/_xpack/migration/assistance`:: deprecated[6.7.0] Returns a list of indices
190
+ that need to be reindexed before you can upgrade to {version}.
191
+ +
192
+ `/_xpack/migration/upgrade`:: deprecated[6.7.0] Upgrades the indices for the
193
+ {watcher} and {security-features} to a single-type format compatible with
194
+ Elasticsearch 6.x.
192
195
193
196
. Once you've resolved all of the migration issues, perform
194
197
a {ref}/rolling-upgrades.html[rolling upgrade] from Elasticsearch 5.6 to {version}.
@@ -223,34 +226,26 @@ these indices must be upgraded to the new format. If you are upgrading from a
223
226
version prior to 5.6, you must upgrade them after after installing
224
227
Elasticsearch {version}.
225
228
226
- To get a list of the indices that need to be upgraded, install {xpack} and use
227
- the {ref}/migration-api-assistance .html[`_migration/assistance` API]:
229
+ To get a list of the indices that need to be upgraded, use the
230
+ {ref}/migration-api-deprecation .html[deprecation info API]:
228
231
229
232
[source,json]
230
233
----------------------------------------------------------
231
- GET /_migration/assistance
234
+ GET /_xpack/migration/deprecations
232
235
----------------------------------------------------------
233
236
// CONSOLE
234
237
235
238
To upgrade the `.security` index:
236
239
237
240
. On a single node, add a temporary superuser account to the `file` realm.
238
- . Use the {ref}/migration-api-upgrade.html[`_migration/upgrade`]
239
- API to upgrade the security index, submitting the request with the credentials
240
- for the temporary superuser:
241
- +
242
- --
243
- [source,json]
244
- ----------------------------------------------------------
245
- POST /_migration/upgrade/.security
246
- ----------------------------------------------------------
247
- // CONSOLE
248
- --
241
+ . Use the {kib} Upgrade Assistant to upgrade the security index, submitting the
242
+ request with the credentials for the temporary superuser. Alternatively, you can
243
+ {ref}/reindex-upgrade.html[reindex manually].
249
244
250
245
. Delete the temporary superuser account from the file realm.
251
246
252
247
You can use your regular administration credentials to upgrade the other
253
- internal indices using the `_migration/upgrade` API .
248
+ internal indices.
254
249
255
250
TIP: Once you upgrade the `.kibana` index, you can run Kibana and use the
256
251
{xpack} Reindex Helper UI to upgrade the other indices.
0 commit comments