# Elastic enterpise search engine count limit

**URL:** <https://discuss.elastic.co/t/elastic-enterpise-search-engine-count-limit/361708>\
**Category:** Elastic Search\
**Created:** [June 19, 2024, 7:50am UTC](https://discuss.elastic.co/t/elastic-enterpise-search-engine-count-limit/361708 "2024-06-19T07:50:45Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![CTO\_Servefast](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cto_servefast/32/131802_2.png) [@CTO\_Servefast](https://discuss.elastic.co/u/CTO_Servefast)\
**Post date:** [June 19, 2024, 7:50am UTC](https://discuss.elastic.co/t/elastic-enterpise-search-engine-count-limit/361708/1 "2024-06-19T07:50:45Z")

</div>

Is there any Elastic Enterpise Search engine count limit. How many engines can i create for example can I have an engine per user. This would help me solve some of the other issues i am having.

Thanks for any help in advance

---

<div class="post-metadata">

**Author:** ![nfeekery](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nfeekery/32/117349_2.png) [@nfeekery](https://discuss.elastic.co/u/nfeekery)\
**Post date:** [June 19, 2024, 8:48am UTC](https://discuss.elastic.co/t/elastic-enterpise-search-engine-count-limit/361708/2 "2024-06-19T08:48:10Z")

</div>

Hi @CTO_Servefast, there's no hard limit for the number of engines in Enterprise Search. Anecdotally I've seen cases with 40+ engines before. However, each engine takes up resources, so how performative it would be really depends on the server specs and what the engines are doing.

---

<div class="post-metadata">

**Author:** ![CTO\_Servefast](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cto_servefast/32/131802_2.png) [@CTO\_Servefast](https://discuss.elastic.co/u/CTO_Servefast)\
**Post date:** [June 19, 2024, 10:08am UTC](https://discuss.elastic.co/t/elastic-enterpise-search-engine-count-limit/361708/3 "2024-06-19T10:08:35Z")

</div>

That is perfect thank you since we are looking to have an engine for each user we will scale and handle servers ofc.

EDIT: actually 40+ not good 🙂 we would need 1000+

---

<div class="post-metadata">

**Author:** ![nfeekery](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nfeekery/32/117349_2.png) [@nfeekery](https://discuss.elastic.co/u/nfeekery)\
**Post date:** [June 19, 2024, 10:22am UTC](https://discuss.elastic.co/t/elastic-enterpise-search-engine-count-limit/361708/4 "2024-06-19T10:22:03Z")

</div>

1000 is huge, I don't think Enterprise Search or Elasticsearch will handle that well. I don't recommend this approach anymore 😄

What is the specific problem you're trying to resolve by having a separate engine for each user?

---

<div class="post-metadata">

**Author:** ![CTO\_Servefast](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cto_servefast/32/131802_2.png) [@CTO\_Servefast](https://discuss.elastic.co/u/CTO_Servefast)\
**Post date:** [June 19, 2024, 10:24am UTC](https://discuss.elastic.co/t/elastic-enterpise-search-engine-count-limit/361708/5 "2024-06-19T10:24:11Z")

</div>

Actually it is quite simple i want to delete all of the files for a user. You can read more here in another topic. I was thinking it might me easier to delete the engine but if i am going to use one engine then i need to delete specific files that are for the user

> [@Get all of the documents for user in elastic enterprise search](https://discuss.elastic.co/t/get-all-of-the-documents-for-user-in-elastic-enterprise-search/361707/2):
>
> Hi @CTO_Servefast The only way i had some success was using client.app.search() using empty string for query but it seems unreliable Can you expand on what makes it seem unreliable? The App Search search query should return all docs ordered by ID by default. If docs are being added, deleted, updated, etc. during the search operation and that search result is paginated, there could be some inconsistencies in the results. You can resolve that by using [point in time API](https://www.elastic.co/guide/en/elasticsearch/reference/current/point-in-time-api.html), but to do this you'd n…

---

<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:** [July 17, 2024, 10:24am UTC](https://discuss.elastic.co/t/elastic-enterpise-search-engine-count-limit/361708/6 "2024-07-17T10:24:33Z")

</div>

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