Skip to content

Commit 9237514

Browse files
committed
Iter
1 parent a087e99 commit 9237514

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

deploy-manage/upgrade/prepare-to-upgrade.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -63,11 +63,11 @@ Review the following best practices to upgrade your deployments.
6363
:::{tip}
6464
During your upgrade tests, pay particular attention to the following aspects:
6565

66-
*Cluster stability*: Does the new version of {{es}} form a stable healthy cluster?
66+
**Cluster stability**: Does the new version of {{es}} form a stable healthy cluster?
6767

68-
*Indexing and search performance*: Does the new version of {{es}} perform the same (or better) than the current one on your specific workload and data?
68+
**Indexing and search performance**: Does the new version of {{es}} perform the same (or better) than the current one on your specific workload and data?
6969

70-
*Snapshots*: Do all of your snapshot repositories work correctly and pass [repository analysis](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-snapshot-repository-analyze)?
70+
**Snapshots**: Do all of your snapshot repositories work correctly and pass [repository analysis](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-snapshot-repository-analyze)?
7171
:::
7272

7373
1. Create a snapshot of your production deployment before starting the upgrade.

0 commit comments

Comments
 (0)