# \[copy\] Data Stop ingesting after deleting index

**URL:** <https://discuss.elastic.co/t/copy-data-stop-ingesting-after-deleting-index/310649>\
**Category:** Elasticsearch\
**Created:** [July 26, 2022, 1:55pm UTC](https://discuss.elastic.co/t/copy-data-stop-ingesting-after-deleting-index/310649 "2022-07-26T13:55:33Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![noa-ru](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/noa-ru/32/107293_2.png) [@noa-ru](https://discuss.elastic.co/u/noa-ru)\
**Post date:** [July 26, 2022, 1:55pm UTC](https://discuss.elastic.co/t/copy-data-stop-ingesting-after-deleting-index/310649/1 "2022-07-26T13:55:33Z")

</div>

Hello all! i not found a solution for my problem, but i found this [post](https://discuss.elastic.co/t/data-stop-ingesting-after-deleting-index/256027) with same problem.  
And when i found a solution, i discovered what i cant write it in this post.  
that's why i registered here and created this post, i hope anyone can searched the answer on this problem.

**Problem is** :  
Data Stop ingesting after deleting index.

no write index is defined for alias. 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.

**Solution** :  
filebeat cant create a needed index;  
we need to look logs of filebeat (or config if you change it) to know whats index pattern-name he try to create;  
in my case this is [filebeat-7.17.0];  
look already created indicies as

```auto
GET _cat/indices/filebeat-7.17.0

```

result:

```auto
yellow open filebeat-7.17.0-2022.02.07-000001 8p2d9dCzRLaep7Ot0oSE3A 1 1 11121533 0 7.1gb 7.1gb
yellow open filebeat-7.17.0-2022.05.08-000004 QU6NFvpaQlqdYhG2fUYahQ 1 1 6114772 0 3.6gb 3.6gb
yellow open filebeat-7.17.0-2022.03.09-000002 TUj4SjfBT7O5zv37S7GUVw 1 1 6293816 0 3.7gb 3.7gb
yellow open filebeat-7.17.0-2022.04.08-000003 Hxl6UBgLTjyrsdSUnqTAGQ 1 1 6237151 0 3.6gb 3.6gb

```

next, create new index as same pattern with current date:

```auto
PUT /filebeat-7.17.0-2022.07.26-000001

```

next, create alias for this indicies

```auto
POST _aliases
{
  "actions": [
    {
      "add": {
        "index": "filebeat-7.17.0-2022.07.26-000001",
        "alias": "filebeat-7.17.0",
        "is_write_index" : true
      }
    }
  ]
}

```

next we need restart the filebeat and he should start writing - problem solved;

I hope this helps those who are facing the same problem.

Also, in my opinion, the platform lacks the functionality of answering unresolved questions. I didn't find any other way than creating a new post

---

<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:** [August 23, 2022, 1:56pm UTC](https://discuss.elastic.co/t/copy-data-stop-ingesting-after-deleting-index/310649/2 "2022-08-23T13:56:30Z")

</div>

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