Index Lifecycle Error - Not Write Index

Elastic Stack Elasticsearch
1

Hello guys, i tried to implement an ilm-policy.
Now i always get the following error:

illegal_argument_exception: source alias [Syslog] does not point to a write index

grafik
grafik806×267 10.3 KB

Now, i don't really get how i make this index my write index. Anybody got an idea how to solve this, without loosing data?

Greets,
Moritz

2

Hi Moritz,

When you created the index, did you already create the alias and mark this index as the "write index" for the alias? This error is stating that the alias exists, but that it doesn't have a designated "write index".

How did you create the alias?

3

I've created the index the following:

PUT logstash-vmw-000001
{
  "aliases": {
  "Syslog": { "is_write_index": true } 
  }
}

I haven't set any shards counts or other settings, since i want to get the ILM to work before that.

4

Interesting, what does this return:

GET /logstash-vmw-000001
5

So i got to fix it now. I messed up big times.
My predecessor put in the alias "Syslog" in both the template for logstash* & for the ILM, after my post i repeatedly got the error that the "alias was found in a template and therefore doubled". I deleted the Alias from the Index-Template, and finally i change my "Index => " Config in my logstash.conf file to the Alias which i would assign later on as my ILM Alias, then i again opened a new Index (deleted the old logstash-vmw-000001) Now it's all working!

Thanks anyway!

6

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.