Skip to content

Commit 6f85729

Browse files
committed
Split snippet file to fix wonky nav
1 parent 70a1ca3 commit 6f85729

File tree

5 files changed

+74
-56
lines changed

5 files changed

+74
-56
lines changed

manage-data/_snippets/ilm-start.md

Lines changed: 29 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,29 @@
1+
If the automatic {{ilm}} or {{slm}} service is not working, you might need to restart the service.
2+
3+
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.
4+
5+
```console
6+
POST _ilm/start
7+
```
8+
9+
The response will look like this:
10+
11+
```console-result
12+
{
13+
"acknowledged": true
14+
}
15+
```
16+
17+
Verify that {{ilm}} is now running:
18+
19+
```console
20+
GET _ilm/status
21+
```
22+
23+
The response will look like this:
24+
25+
```console-result
26+
{
27+
"operation_mode": "RUNNING"
28+
}
29+
```
Lines changed: 15 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
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):
2+
3+
```console
4+
GET _ilm/status
5+
```
6+
7+
Under normal operation, the response shows {{ilm-init}} is `RUNNING`:
8+
9+
```console-result
10+
{
11+
"operation_mode": "RUNNING"
12+
}
13+
```
14+
15+
You can also [](/manage-data/lifecycle/index-lifecycle-management/policy-view-status.md) for further information.
Lines changed: 0 additions & 54 deletions
Original file line numberDiff line numberDiff line change
@@ -1,25 +1,3 @@
1-
Follow these steps to check the current {{ilm-init}} status, and to stop or restart it as needed.
2-
3-
### Get {{ilm-init}} status
4-
5-
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):
6-
7-
```console
8-
GET _ilm/status
9-
```
10-
11-
Under normal operation, the response shows {{ilm-init}} is `RUNNING`:
12-
13-
```console-result
14-
{
15-
"operation_mode": "RUNNING"
16-
}
17-
```
18-
19-
You can also [](/manage-data/lifecycle/index-lifecycle-management/policy-view-status.md) for further information.
20-
21-
### Stop {{ilm-init}}
22-
231
By default, the {{ilm}} service is in the `RUNNING` state and manages all indices that have lifecycle policies.
242

253
You can stop {{ilm-init}} 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.
@@ -64,36 +42,4 @@ Once all policies are at a safe stopping point, {{ilm-init}} moves into the `STO
6442
{
6543
"operation_mode": "STOPPED"
6644
}
67-
```
68-
69-
### Start {{ilm-init}} [start-ilm]
70-
71-
If the automatic {{ilm}} or {{slm}} service is not working, you might need to restart the service.
72-
73-
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.
74-
75-
```console
76-
POST _ilm/start
77-
```
78-
79-
The response will look like this:
80-
81-
```console-result
82-
{
83-
"acknowledged": true
84-
}
85-
```
86-
87-
Verify that {{ilm}} is now running:
88-
89-
```console
90-
GET _ilm/status
91-
```
92-
93-
The response will look like this:
94-
95-
```console-result
96-
{
97-
"operation_mode": "RUNNING"
98-
}
9945
```

manage-data/lifecycle/index-lifecycle-management/start-stop-index-lifecycle-management.md

Lines changed: 15 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,5 +10,19 @@ products:
1010

1111
# Start and stop index lifecycle management [start-stop-ilm]
1212

13-
:::{include} /manage-data/_snippets/start-stop-ilm.md
13+
Follow these steps to check the current {{ilm-init}} status, and to stop or restart it as needed.
14+
15+
### Get {{ilm-init}} status
16+
17+
:::{include} /manage-data/_snippets/ilm-status.md
18+
:::
19+
20+
### Stop {{ilm-init}}
21+
22+
:::{include} /manage-data/_snippets/ilm-stop.md
23+
:::
24+
25+
### Start {{ilm-init}}
26+
27+
:::{include} /manage-data/_snippets/ilm-start.md
1428
:::

troubleshoot/elasticsearch/start-ilm.md

Lines changed: 15 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -121,5 +121,19 @@ The response will look like this:
121121

122122
## Check status, stop, and restart {{ilm-init}} [check-stop-start-ilm]
123123

124-
:::{include} ../../manage-data/_snippets/start-stop-ilm.md
124+
Follow these steps to check the current {{ilm-init}} status, and to stop or restart it as needed.
125+
126+
### Get {{ilm-init}} status
127+
128+
:::{include} ../../manage-data/_snippets/ilm-status.md
129+
:::
130+
131+
### Stop {{ilm-init}}
132+
133+
:::{include} ../../manage-data/_snippets/ilm-stop.md
134+
:::
135+
136+
### Start {{ilm-init}}
137+
138+
:::{include} ../../manage-data/_snippets/ilm-start.md
125139
:::

0 commit comments

Comments
 (0)