AClerk
March 23, 2021, 12:07am
6
How did you apply the settings?
Some discussions:
Had the same thing happen.
If you use the rollover API manually to do the rollover instead of using your ILM policy, each time the policy runs it will throw this error. This happens because the index is not being flagged as complete, when the policy runs it appears to be trying to manage the index but it's not flagged as writable.
Add "index.lifecycle.indexing_complete": "true" to the index in question, then clear the error by retrying the policy. When the policy next runs(default is every 1…
Hi,
After installation on 1 filebeat agent to a new 7.4.1 Elastic cluster, I have the following errors on my filebeat indices:
Index lifecycle error
illegal_argument_exception: index [filebeat-7.4.1-2019.11.04] is not the write index for alias [filebeat-7.4.1]
GET filebeat-7.4.1/_ilm/explain
"filebeat-7.4.1-2019.11.04" : {
"index" : "filebeat-7.4.1-2019.11.04",
"managed" : true,
"policy" : "filebeat-7.4.1",
"lifecycle_date_millis" : 1572822004864,
"age" : "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]
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