# Engine Name is already Taken

**URL:** <https://discuss.elastic.co/t/engine-name-is-already-taken/306961>\
**Category:** Elastic Search\
**Created:** [June 12, 2022, 2:51pm UTC](https://discuss.elastic.co/t/engine-name-is-already-taken/306961 "2022-06-12T14:51:00Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![Artem\_Shelkovnikov](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/artem_shelkovnikov/32/134322_2.png) [@Artem\_Shelkovnikov](https://discuss.elastic.co/u/Artem_Shelkovnikov)\
**Post date:** [July 4, 2022, 2:45pm UTC](https://discuss.elastic.co/t/engine-name-is-already-taken/306961/12 "2022-07-04T14:45:26Z")

</div>

It actually exposed the place where the uniqueness constraint takes place, it's this index: `.ent-search-actastic-search_indices_v1`.

I suppose, that you can query it to confirm that the index is there:

```auto
GET .ent-search-actastic-search_indices_v1/_search
{
  "query": {
    "term": {
      "name": {
        "value": "np-local-search-np-lt-11-brisbane"
      }
    }
  }
}

```

If the index is there, you can then drop it:

```auto
DELETE .ent-search-actastic-search_indices_v1/_doc/<INDEX_ID_FROM_PREVIOUS_STEP>

```

It's something that can happen when Enterprise Search is overloaded, crashes in the middle of index creation or if Elasticsearch goes away during creation of index. It's not something that should happen during normal work with Enterprise Search, though.

---

_[View the full topic](https://discuss.elastic.co/t/engine-name-is-already-taken/306961)._