Skip to content

Commit 95c96d6

Browse files
committed
[DOCS] Deprecates migration assistance and upgrade APIs (#247)
1 parent 8172466 commit 95c96d6

File tree

1 file changed

+15
-20
lines changed

1 file changed

+15
-20
lines changed

docs/en/install-upgrade/upgrading-stack.asciidoc

Lines changed: 15 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -183,12 +183,15 @@ need to be migrated or deleted, and upgrade the internal indices to the
183183
+
184184
You can also call the Elasticsearch migration APIs directly:
185185
+
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.
189188
+
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.
192195

193196
. Once you've resolved all of the migration issues, perform
194197
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
223226
version prior to 5.6, you must upgrade them after after installing
224227
Elasticsearch {version}.
225228

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]:
228231

229232
[source,json]
230233
----------------------------------------------------------
231-
GET /_migration/assistance
234+
GET /_xpack/migration/deprecations
232235
----------------------------------------------------------
233236
// CONSOLE
234237

235238
To upgrade the `.security` index:
236239

237240
. 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].
249244

250245
. Delete the temporary superuser account from the file realm.
251246

252247
You can use your regular administration credentials to upgrade the other
253-
internal indices using the `_migration/upgrade` API.
248+
internal indices.
254249

255250
TIP: Once you upgrade the `.kibana` index, you can run Kibana and use the
256251
{xpack} Reindex Helper UI to upgrade the other indices.

0 commit comments

Comments
 (0)