# Disk Full problem winlogbeat

**URL:** <https://discuss.elastic.co/t/disk-full-problem-winlogbeat/252749>\
**Category:** Elasticsearch\
**Created:** [October 21, 2020, 1:04am UTC](https://discuss.elastic.co/t/disk-full-problem-winlogbeat/252749 "2020-10-21T01:04:24Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![pablo1816](https://avatars.discourse-cdn.com/v4/letter/p/ccd318/32.png) [@pablo1816](https://discuss.elastic.co/u/pablo1816)\
**Post date:** [October 21, 2020, 1:04am UTC](https://discuss.elastic.co/t/disk-full-problem-winlogbeat/252749/1 "2020-10-21T01:04:24Z")

</div>

I was running out of space on node and deleted multiple indexes, now there is space but in winlogbeat I have the following error.

2020-10-20T21:51:15.360-0300 ERROR [elasticsearch] elasticsearch/client.go:213 Failed to perform any bulk index operations: 400 Bad Request: {"error":{"root\_cause":[{"type":"illegal\_argument\_exception","reason":"no write index is defined for alias [winlogbeat-7.7.0]. The write index may be explicitly disabled using is\_write\_index=false or the alias points to multiple indices without one being designated as a write index"}],"type":"illegal\_argument\_exception","reason":"no write index is defined for alias [winlogbeat-7.7.0]. The write index may be explicitly disabled using is\_write\_index=false or the alias points to multiple indices without one being designated as a write index"},"status":400}

---

<div class="post-metadata">

**Author:** ![Wolfram\_Haussig](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/wolfram_haussig/32/70528_2.png) [@Wolfram\_Haussig](https://discuss.elastic.co/u/Wolfram_Haussig)\
**Post date:** [October 21, 2020, 11:19am UTC](https://discuss.elastic.co/t/disk-full-problem-winlogbeat/252749/2 "2020-10-21T11:19:43Z")

</div>

Hello Pablo,

You seem to have enabled Index Lifecycle management and deleted the active index. ILM works by having an alias `winlogbeat-7.7.0` which points to one or more indexes but it has only 1 active index where the incoming data is written to.  
As a solution you have to bootstrap the write index [manually](https://www.elastic.co/guide/en/elasticsearch/reference/current/getting-started-index-lifecycle-management.html#ilm-gs-alias-bootstrap) (the number might change depending on how many indexes are already created and how you configured your ILM settings):

```auto
PUT winlogbeat-7.7.0-000001
{
  "aliases": {
    "winlogbeat-7.7.0": {
      "is_write_index": true
    }
  }
}

```

Best regards  
Wolfram

---

<div class="post-metadata">

**Author:** ![pablo1816](https://avatars.discourse-cdn.com/v4/letter/p/ccd318/32.png) [@pablo1816](https://discuss.elastic.co/u/pablo1816)\
**Post date:** [October 21, 2020, 6:04pm UTC](https://discuss.elastic.co/t/disk-full-problem-winlogbeat/252749/3 "2020-10-21T18:04:50Z")

</div>

Thanks, it worked well.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [November 18, 2020, 6:04pm UTC](https://discuss.elastic.co/t/disk-full-problem-winlogbeat/252749/4 "2020-11-18T18:04:54Z")

</div>

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