# Does single node Elasticsearch supports ILM ploicy

**URL:** <https://discuss.elastic.co/t/does-single-node-elasticsearch-supports-ilm-ploicy/350124>\
**Category:** Kibana\
**Created:** [December 29, 2023, 11:46am UTC](https://discuss.elastic.co/t/does-single-node-elasticsearch-supports-ilm-ploicy/350124 "2023-12-29T11:46:20Z")\
**Posts on this page:** 20\
**Page:** 2

<div class="post-metadata">

**Author:** ![Ravi\_Pattar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ravi_pattar/32/124209_2.png) [@Ravi\_Pattar](https://discuss.elastic.co/u/Ravi_Pattar)\
**Post date:** [January 9, 2024, 7:03pm UTC](https://discuss.elastic.co/t/does-single-node-elasticsearch-supports-ilm-ploicy/350124/21 "2024-01-09T19:03:06Z")

</div>

> [@stephenb](#):
>
> Share your entire filebeat.yml please...

Please find the details about filebeat.yml in the below link.

> **[filebeat.yml - Pastebin.com](https://pastebin.com/5J60A58w)**
>
> Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.

---

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [January 9, 2024, 7:24pm UTC](https://discuss.elastic.co/t/does-single-node-elasticsearch-supports-ilm-ploicy/350124/22 "2024-01-09T19:24:16Z")

</div>

Ohhh you are going through logstash...

You did not mention that... do you need logstash? its adds complexity... and is why your ILM is not working

Its OK but this means you have an issue there...

Share your logstash conf file... particularly the output.

Or take out logstash and go directly to Filebeat -\> Elasticsearch

Anyway... your old indices will never roll over and get deleted because they were not set up correctly because you put logstash in the middle and did not configure it correctly ...

You need to run  
`./filebeat setup -e`  
When filebeat is pointing to elasticsearch

Then change Filebeat to point to logstash and then use the correct config

AND yes the docs are wrong (I thought I had them fix it)

it should look like (notice the `index` name)

So you probably followed the docs bu they are not correct.

```auto
output {
  if [@metadata][pipeline] {
    elasticsearch {
      hosts => "https://061ab24010a2482e9d64729fdb0fd93a.us-east-1.aws.found.io:9243"
      manage_template => false
      index => "%{[@metadata][beat]}-%{[@metadata][version]}"
      pipeline => "%{[@metadata][pipeline]}" 
      user => "elastic"
      password => "secret"
    }
  } else {
    elasticsearch {
      hosts => "https://061ab24010a2482e9d64729fdb0fd93a.us-east-1.aws.found.io:9243"
      manage_template => false
      index => "%{[@metadata][beat]}-%{[@metadata][version]}"
      user => "elastic"
      password => "secret"
    }
  }
}

```

---

<div class="post-metadata">

**Author:** ![Ravi\_Pattar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ravi_pattar/32/124209_2.png) [@Ravi\_Pattar](https://discuss.elastic.co/u/Ravi_Pattar)\
**Post date:** [January 9, 2024, 7:38pm UTC](https://discuss.elastic.co/t/does-single-node-elasticsearch-supports-ilm-ploicy/350124/23 "2024-01-09T19:38:58Z")

</div>

> [@stephenb](#):
>
> Share your logstash conf file... particularly the output.

cat 30-elasticsearch-output.conf

```auto
output {
  if [@metadata][pipeline] {
        elasticsearch {
        hosts => ["localhost:9200"]
        manage_template => false
        index => "%{[@metadata][beat]}-%{[@metadata][version]}-%{+YYYY.MM.dd}"
        pipeline => "%{[@metadata][pipeline]}"
        }
  } else {
        elasticsearch {
        hosts => ["localhost:9200"]
        manage_template => false
        index => "%{[@metadata][beat]}-%{[@metadata][version]}-%{+YYYY.MM.dd}"
        }
  }
}

```

---

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [January 9, 2024, 7:43pm UTC](https://discuss.elastic.co/t/does-single-node-elasticsearch-supports-ilm-ploicy/350124/24 "2024-01-09T19:43:56Z")

</div>

Should be .... the following... if you want ILM to work.

Your logstash config is wrong it is meant for daily indices not ILM.

This should work going forward... your other indices will never roll over because they are "Daily Indices" and are not using the Write Alias which is

`filebeat-7.17.13`  
hence  
` index => "%{[@metadata][beat]}-%{[@metadata][version]}"`

Correct

```auto
output {
  if [@metadata][pipeline] {
        elasticsearch {
        hosts => ["localhost:9200"]
        manage_template => false
        index => "%{[@metadata][beat]}-%{[@metadata][version]}"
        pipeline => "%{[@metadata][pipeline]}"
        }
  } else {
        elasticsearch {
        hosts => ["localhost:9200"]
        manage_template => false
        index => "%{[@metadata][beat]}-%{[@metadata][version]}"
        }
  }
}

```

You will need to manually delete the old indices as they will never rollover and thus never move to the next step and never be deleted

To be direct the Guide you are following was intended to use Daily Indices not ILM... until now .. we did not know that... and that is the source of most of these issues.

You still need to run  
`./filebeat setup -e`  
At least once while filebeat is pointing to Elasticsearch _ **BEFORE** _ you start sending data through logstash.

See it should look like this you are missing all the write alias ....

```auto
GET /filebeat-7.17.3-2024.01.09-000001
{
  "filebeat-7.17.3-2024.01.09-000001" : {
    "aliases" : { <!--- THIS
      "filebeat-7.17.3" : { <!--- THIS
        "is_write_index" : true <!--- THIS
      }
    },

```

---

<div class="post-metadata">

**Author:** ![Ravi\_Pattar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ravi_pattar/32/124209_2.png) [@Ravi\_Pattar](https://discuss.elastic.co/u/Ravi_Pattar)\
**Post date:** [January 10, 2024, 4:59am UTC](https://discuss.elastic.co/t/does-single-node-elasticsearch-supports-ilm-ploicy/350124/25 "2024-01-10T04:59:00Z")

</div>

Thanks, Stephen.

I will check and update on my findings.

---

<div class="post-metadata">

**Author:** ![Ravi\_Pattar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ravi_pattar/32/124209_2.png) [@Ravi\_Pattar](https://discuss.elastic.co/u/Ravi_Pattar)\
**Post date:** [January 11, 2024, 6:14pm UTC](https://discuss.elastic.co/t/does-single-node-elasticsearch-supports-ilm-ploicy/350124/26 "2024-01-11T18:14:25Z")

</div>

Hi @stephenb

I have a query on the below and this is specific to production environment.

1. Does ILM supported on the basic version of ELK (7.17.15)?

2. Does the attached in the below URL is also having issues? Because I am seeing exceptions when I run GET /filebeat-7.17.15-2024.01.10/\_ilm/explain.

> **[Hastebin](https://hastebin.com/share/ohaxutafec.bash)**
>
> Hastebin is a free web-based pastebin service for storing and sharing text and code snippets with anyone. Get started now.

1. The existing production setup has implementation as filebeat \> Logstash \> Elasticsearch  
And taking out logstash to make ILM work may not be feasible at the moment.

2. Since the indices are piling up on daily basis result in huge disk utilization. do we have a solution on how this can sorted out? Please suggest.

Thanks,

---

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [January 11, 2024, 6:27pm UTC](https://discuss.elastic.co/t/does-single-node-elasticsearch-supports-ilm-ploicy/350124/27 "2024-01-11T18:27:53Z")

</div>

> [@Ravi\_Pattar](#):
>
> Does ILM supported on the basic version of ELK (7.17.15)?

Yes Absolutely

> [@Ravi\_Pattar](#):
>
> Does the attached in the below URL is also having issues? Because I am seeing exceptions when I run GET /filebeat-7.17.15-2024.01.10/\_ilm/explain.

That is EXACTLY what I am trying to explain ... you have Setup ILM vs Daily Indices and are mixing the concept ... and this is causing the errors.... you following a 3rd party doc / config which does NOT support what you want to do...

But It can be easily fixed if you follow my instructions.

> [@Ravi\_Pattar](#):
>
> The existing production setup has implementation as filebeat \> Logstash \> Elasticsearch  
> And taking out logstash to make ILM work may not be feasible at the moment.

That is fine I gave you the solution above... with the output section that will fix your ILM issue for indices going forward it will NOT fix the old broken indices.

Replace your output section with what I gave you AND ILM should start working

BUT you need to run

`filebeat setup -e`

FIRST before you send the data through logstash

Then your ILM will work as you want.

Can you run

`GET _alias/filebeat*`

And show the result please

This can be fixed but you actually need to do what I am suggesting otherwise it will _ **never** _ work

> [@Ravi\_Pattar](#):
>
> Since the indices are piling up on daily basis result in huge disk utilization. do we have a solution on how this can sorted out? Please suggest.

You will need to delete them manually... which is easy to do using

`DELETE indexname`

WARNING that will permanently delete the indices and the data will be lost

---

<div class="post-metadata">

**Author:** ![Ravi\_Pattar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ravi_pattar/32/124209_2.png) [@Ravi\_Pattar](https://discuss.elastic.co/u/Ravi_Pattar)\
**Post date:** [January 11, 2024, 6:35pm UTC](https://discuss.elastic.co/t/does-single-node-elasticsearch-supports-ilm-ploicy/350124/28 "2024-01-11T18:35:23Z")

</div>

> [@stephenb](#):
>
> Can you run
> 
> `GET _alias/filebeat*`
> 
> And show the result please

Thanks, Stephen for your quick response. Please find the details below.

```auto
{
  "filebeat-7.17.15-2024.01.05-000003" : {
    "aliases" : {
      "filebeat-7.17.15" : {
        "is_write_index" : true
      }
    }
  },
  "filebeat-7.17.15-2023.12.29-000002" : {
    "aliases" : {
      "filebeat-7.17.15" : {
        "is_write_index" : false
      }
    }
  }
}

```

---

<div class="post-metadata">

**Author:** ![Ravi\_Pattar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ravi_pattar/32/124209_2.png) [@Ravi\_Pattar](https://discuss.elastic.co/u/Ravi_Pattar)\
**Post date:** [January 11, 2024, 7:13pm UTC](https://discuss.elastic.co/t/does-single-node-elasticsearch-supports-ilm-ploicy/350124/29 "2024-01-11T19:13:59Z")

</div>

Hi Stephen

Another thing that I have prepared the procedural doc on applying the changes as per your suggestions on the test instance.

Please review the doc from the link below and please let me know if its correct so that I can start applying changes.

> **[Hastebin](https://hastebin.com/share/etigepojop.perl)**
>
> Hastebin is a free web-based pastebin service for storing and sharing text and code snippets with anyone. Get started now.

> [@stephenb](#):
>
> BUT you need to run
> 
> `filebeat setup -e`
> 
> FIRST before you send the data through logstash

After running the filebeat setup -e. do I need to revert the changes in filebeat.yml again i.e. pointing filbeat -\> Logstash

Thanks,

---

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [January 11, 2024, 7:22pm UTC](https://discuss.elastic.co/t/does-single-node-elasticsearch-supports-ilm-ploicy/350124/30 "2024-01-11T19:22:45Z")

</div>

> [@Ravi\_Pattar](#):
>
> ```auto
> {
> "filebeat-7.17.15-2024.01.05-000003" : {
> "aliases" : {
> "filebeat-7.17.15" : {
> "is_write_index" : true
> }
> }
> }
> ...
> }
> 
> ```

This is good it means you have a viable write alias...

> [@Ravi\_Pattar](#):
>
> Please review the doc from the link below and please let me know if its correct so that I can start applying changes.

Hi Ravi... quick look ... not quite right...

Steps Should be

1. Fix Logstash output
2. Point filebeat output to elasticsearch
3. `./filebeat setup -e` (your command is not correct)
4. Point filebeat output back to logstash
5. Start Filebeat

You will need to test and try... I am not really have time to review all your procedures...

---

<div class="post-metadata">

**Author:** ![Ravi\_Pattar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ravi_pattar/32/124209_2.png) [@Ravi\_Pattar](https://discuss.elastic.co/u/Ravi_Pattar)\
**Post date:** [January 11, 2024, 7:50pm UTC](https://discuss.elastic.co/t/does-single-node-elasticsearch-supports-ilm-ploicy/350124/31 "2024-01-11T19:50:28Z")

</div>

Hi Stephen

I have run the procedure and I could see as below when compared to yours in previous post.

> [@stephenb](#):
>
> See it should look like this you are missing all the write alias ....
> 
> ```auto
> GET /filebeat-7.17.3-2024.01.09-000001
> {
> "filebeat-7.17.3-2024.01.09-000001" : {
> "aliases" : { <!--- THIS
> "filebeat-7.17.3" : { <!--- THIS
> "is_write_index" : true <!--- THIS
> }
> },
> 
> ```

Latest from my test instance as below.

GET filebeat-7.17.13-2024.01.09-000006

```auto
{
  "filebeat-7.17.13-2024.01.09-000006" : {
    "aliases" : {
      "filebeat-7.17.13" : {
        "is_write_index" : true
      }
    },

```

---

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [January 11, 2024, 8:15pm UTC](https://discuss.elastic.co/t/does-single-node-elasticsearch-supports-ilm-ploicy/350124/32 "2024-01-11T20:15:08Z")

</div>

So now if you configure logstash output as I suggested...

Logstash will write data to the write alias `filebeat-7.17.13` (which points to the concrete index), and your ILM, rollover and delete should work per the policy...

In order for ILM to work... the data needs to be written to the write alias...

I would also suggest to run this.

`POST filebeat-7.17.3/_rollover`

That will force the write alias to to rollover the index, and the new index will follow your new ILM Policy, and you should be good to go!

---

<div class="post-metadata">

**Author:** ![Ravi\_Pattar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ravi_pattar/32/124209_2.png) [@Ravi\_Pattar](https://discuss.elastic.co/u/Ravi_Pattar)\
**Post date:** [January 11, 2024, 8:25pm UTC](https://discuss.elastic.co/t/does-single-node-elasticsearch-supports-ilm-ploicy/350124/33 "2024-01-11T20:25:22Z")

</div>

> [@stephenb](#):
>
> I would also suggest to run this.
> 
> `POST filebeat-7.17.3/_rollover`

POST filebeat-7.17.13/\_rollover

```auto
{
  "acknowledged" : true,
  "shards_acknowledged" : true,
  "old_index" : "filebeat-7.17.13-2024.01.11-000007",
  "new_index" : "filebeat-7.17.13-2024.01.11-000008",
  "rolled_over" : true,
  "dry_run" : false,
  "conditions" : { }
}

```

---

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [January 11, 2024, 8:27pm UTC](https://discuss.elastic.co/t/does-single-node-elasticsearch-supports-ilm-ploicy/350124/34 "2024-01-11T20:27:07Z")

</div>

You should be good to go... Looks like a new index what just created today anyways but that should not matter...

Start Logstash with the Config  
Point Filebeat to Logstash  
And you should see data flowing into `filebeat-7.17.13-2024.01.11-000008`

---

<div class="post-metadata">

**Author:** ![Ravi\_Pattar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ravi_pattar/32/124209_2.png) [@Ravi\_Pattar](https://discuss.elastic.co/u/Ravi_Pattar)\
**Post date:** [January 11, 2024, 8:47pm UTC](https://discuss.elastic.co/t/does-single-node-elasticsearch-supports-ilm-ploicy/350124/35 "2024-01-11T20:47:16Z")

</div>

> [@stephenb](#):
>
> Point Filebeat to Logstash

This was done. reference output below.

```auto
# ------------------------------ Logstash Output -------------------------------
output.logstash:
  # The Logstash hosts
  hosts: ["localhost:5044"]

```

> [@stephenb](#):
>
> Start Logstash with the Config

You mean as below..

```auto
root@ELK-test:/usr/share/logstash# bin/logstash -f /etc/logstash/conf.d/30-elasticsearch-output.conf

```

But it give some errors. file attached in the below URL.

> **[Hastebin](https://hastebin.com/share/xawalahebe.ruby)**
>
> Hastebin is a free web-based pastebin service for storing and sharing text and code snippets with anyone. Get started now.

> [@stephenb](#):
>
> And you should see data flowing into `filebeat-7.17.13-2024.01.11-000008`

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/5/0/50b9135e29d383f725999934d30ffb04c57602b8.png)

---

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [January 11, 2024, 8:50pm UTC](https://discuss.elastic.co/t/does-single-node-elasticsearch-supports-ilm-ploicy/350124/36 "2024-01-11T20:50:32Z")

</div>

You need to start logstash the normal way... probably

`systemctl start logstash`

I feel like I am helping in the dark.....

I am not following your guide (you have not shared it... but also we recommend following our documentation) so I have no clue how you installed logstash and what you did with logstash etc.etc...

If you have questions on starting / stopping running logstash etc... you should open a separate thread on that...

---

<div class="post-metadata">

**Author:** ![Ravi\_Pattar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ravi_pattar/32/124209_2.png) [@Ravi\_Pattar](https://discuss.elastic.co/u/Ravi_Pattar)\
**Post date:** [January 11, 2024, 8:57pm UTC](https://discuss.elastic.co/t/does-single-node-elasticsearch-supports-ilm-ploicy/350124/37 "2024-01-11T20:57:23Z")

</div>

> [@stephenb](#):
>
> You need to start logstash the normal way... probably
> 
> `systemctl start logstash`

yeah, I have restarted the LS service and now its up and running.

```auto
# systemctl status logstash
● logstash.service - logstash
     Loaded: loaded (/etc/systemd/system/logstash.service; enabled; vendor preset: enabled)
     Active: active (running) since Thu 2024-01-11 20:52:15 UTC; 2s ago
   Main PID: 5293 (java)
      Tasks: 14 (limit: 4667)

```

> [@stephenb](#):
>
> I am not following your guide (you have not shared it... but also we recommend following our documentation) so I have no clue how you installed logstash and what you did with logstash etc.etc...

I have followed the guide from the sources on the installation of ELK stack.

> **[How to Install ELK Stack on Ubuntu 18.04 / 20.04 | PhoenixNAP KB](https://phoenixnap.com/kb/how-to-install-elk-stack-on-ubuntu)**
>
> A step-by-step tutorial on how to install the ELK stack on Ubuntu. Elasticsearch, Logstash, and Kibana are the go-to tools for real-time monitoring logs.

> [@stephenb](#):
>
> but also we recommend following our documentation

would request you to share your documentation which will be of a great help.

Thanks,

---

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [January 11, 2024, 9:05pm UTC](https://discuss.elastic.co/t/does-single-node-elasticsearch-supports-ilm-ploicy/350124/38 "2024-01-11T21:05:45Z")

</div>

So that "HowTo" looks like it _ **was** _ pretty good... but it is ~3.5+ years old... Elastic moves fast so that is an issue... and why the new ILM did not work with the old config etc..

> [@Ravi\_Pattar](#):
>
> would request you to share your documentation which will be of a great help.

There are many many resources ...

> **[Elastic documentation | Elastic](https://www.elastic.co/guide/index.html)**

[https://www.elastic.co/learn](https://www.elastic.co/learn)

I am sure you can look around you are doing fine... just keep working and asking questions

Good Luck!

---

<div class="post-metadata">

**Author:** ![Ravi\_Pattar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ravi_pattar/32/124209_2.png) [@Ravi\_Pattar](https://discuss.elastic.co/u/Ravi_Pattar)\
**Post date:** [January 11, 2024, 9:14pm UTC](https://discuss.elastic.co/t/does-single-node-elasticsearch-supports-ilm-ploicy/350124/39 "2024-01-11T21:14:30Z")

</div>

Thanks, Stephen for your guidance and support on this thread.

I will keep posted on my observations on post changes today.

---

<div class="post-metadata">

**Author:** ![Ravi\_Pattar](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ravi_pattar/32/124209_2.png) [@Ravi\_Pattar](https://discuss.elastic.co/u/Ravi_Pattar)\
**Post date:** [January 12, 2024, 4:59pm UTC](https://discuss.elastic.co/t/does-single-node-elasticsearch-supports-ilm-ploicy/350124/40 "2024-01-12T16:59:07Z")

</div>

> [@stephenb](#):
>
> See it should look like this you are missing all the write alias ....
> 
> ```auto
> GET /filebeat-7.17.3-2024.01.09-000001
> {
> "filebeat-7.17.3-2024.01.09-000001" : {
> "aliases" : { <!--- THIS
> "filebeat-7.17.3" : { <!--- THIS
> "is_write_index" : true <!--- THIS
> }
> },
> 
> ```

Hi Stephen,

ILM is working as expected in the test environment and thanks for your guidance on the same.

I am planning to implement the same in the production system today. Currently I came across with the below observations.

```auto
GET /filebeat-8.10.4-2024.01.12

{
  "filebeat-8.10.4-2024.01.12" : {
    "aliases" : { },
    "mappings" : {
      "properties" : {
        "@timestamp" : {
          "type" : "date"
        },

```

```auto
GET /filebeat-8.11.2-2024.01.12

{
  "filebeat-8.11.2-2024.01.12" : {
    "aliases" : { },
    "mappings" : {
      "properties" : {
        "@timestamp" : {
          "type" : "date"
        },

```

Also w.r.t 7.7.15 for which I am planning to run the steps for ILM the GET request shows as below. And I can handle this case as I have did this in test bed yesterday only.

GET /\<filebeat-7.17.15\>

```auto
{
  "filebeat-7.17.15-2024.01.05-000003" : {
    "aliases" : {
      "filebeat-7.17.15" : {
        "is_write_index" : false
      }

```

so, in these conditions mentioned above for index 8.10 and 8.11. How to handle when it comes to rollover e.g. `POST filebeat-7.17.3/_rollover`

Thanks,

[Previous page](https://discuss.elastic.co/t/does-single-node-elasticsearch-supports-ilm-ploicy/350124.md?page=1)

[Next page](https://discuss.elastic.co/t/does-single-node-elasticsearch-supports-ilm-ploicy/350124.md?page=3)