Skip to content

Commit 519b230

Browse files
committed
fixup
1 parent 252cfd8 commit 519b230

File tree

1 file changed

+12
-14
lines changed

1 file changed

+12
-14
lines changed

troubleshoot/elasticsearch/start-ilm.md

Lines changed: 12 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -36,13 +36,13 @@ All of the procedures on this page use the {{es}} APIs. To run these steps using
3636

3737
4. Use the Dev Tools Console to run the API requests as described.
3838

39-
## Check status, stop, and restart {{ilm-init}} [check-stop-start-ilm]
39+
## Check status, stop, and restart {{ilm-init}} [check-stop-start-ilm]
4040

41-
Follow these steps to check the current {{ilm-init}} status, and to start or restop the lifecycle management as needed.
41+
Follow these steps to check the current {{ilm-init}} status, and to stop or restart it as needed.
4242

4343
### Get {{ilm-init}} status
4444

45-
To see the current status of the {{ilm-init}} service, use the [Get Status API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-ilm-get-status):
45+
To see the current status of the {{ilm-init}} service, use the [{{ilm-init}} status API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-ilm-get-status):
4646

4747
```console
4848
GET _ilm/status
@@ -60,7 +60,7 @@ Under normal operation, the response shows {{ilm-init}} is `RUNNING`:
6060

6161
You can stop {{ilm}} to suspend management operations for all indices. For example, you might stop {{ilm}} when performing scheduled maintenance or making changes to the cluster that could impact the execution of {{ilm-init}} actions.
6262

63-
To stop the {{ilm-init}} service and pause execution of all lifecycle policies, use the [Stop API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-ilm-stop):
63+
To stop the {{ilm-init}} service and pause execution of all lifecycle policies, use the [{{ilm-init}} stop API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-ilm-stop):
6464

6565
```console
6666
POST _ilm/stop
@@ -104,9 +104,9 @@ When you stop {{ilm-init}}, [{{slm-init}}](/deploy-manage/tools/snapshot-and-res
104104

105105
### Start {{ilm-init}} [start-ilm]
106106

107-
If the automatic {{ilm}} or {{slm}} service is not working, you might need to start the service.
107+
If the automatic {{ilm}} or {{slm}} service is not working, you might need to restart the service.
108108

109-
To restart {{ilm-init}} and resume executing policies, use the [Start API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-ilm-start). This puts the {{ilm-init}} service in the `RUNNING` state and {{ilm-init}} begins executing policies from where it left off.
109+
To restart {{ilm-init}} and resume executing policies, use the [{{ilm-init}} start API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-ilm-start). This puts the {{ilm-init}} service in the `RUNNING` state and {{ilm-init}} begins executing policies from where it left off.
110110

111111
```console
112112
POST _ilm/start
@@ -136,11 +136,11 @@ The response will look like this:
136136

137137
## Check status, stop, and restart {{slm-init}} [check-stop-start-slm]
138138

139-
Follow these steps to check the current {{slm-init}} status, and to start or restop the lifecycle management as needed.
139+
Follow these steps to check the current {{slm-init}} status, and to stop or restart it as needed.
140140

141141
### Get {{slm-init}} status
142142

143-
To see the current status of the {{slm-init}} service, use the [Get Status API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-slm-get-status):
143+
To see the current status of the {{slm-init}} service, use the [{{slm-init}} status API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-slm-get-status):
144144

145145
```console
146146
GET _slm/status
@@ -156,10 +156,10 @@ Under normal operation, the response shows {{slm-init}} is `RUNNING`:
156156

157157
### Stop {{slm-init}}
158158

159-
You can stop {{slm}} to suspend management operations for all snapshot. For example, you might stop {{slm}} o prevent it from taking scheduled snapshots during maintenance or when making cluster changes that could be impacted by snapshot operations.
159+
You can stop {{slm}} to suspend management operations for all snapshots. For example, you might stop {{slm-init}} to prevent it from taking scheduled snapshots during maintenance or when making cluster changes that could be impacted by snapshot operations.
160160

161161

162-
To stop the {{slm-init}} service and pause execution of all lifecycle policies, use the [Stop API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-slm-stop):
162+
To stop the {{slm-init}} service and pause execution of all lifecycle policies, use the [{{slm-init}} stop API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-slm-stop):
163163

164164
```console
165165
POST _slm/stop
@@ -191,11 +191,9 @@ The response will look like this:
191191

192192
### Start {{slm}} [start-slm]
193193

194-
In the event that automatic snapshot lifecycle management is disabled, new backup snapshots will not be created automatically.
194+
In the event that automatic {{slm}} is disabled, new backup snapshots will not be created automatically.
195195

196-
Follow these steps to start the snapshot lifecycle management service:
197-
198-
[Start](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-slm-start) {{slm}}:
196+
To restart the {{slm-init}} service, use the [{{slm-init}} start API](https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-slm-start).
199197

200198
```console
201199
POST _slm/start

0 commit comments

Comments
 (0)