# Uploading more than 15 engines in meta engine

**URL:** <https://discuss.elastic.co/t/uploading-more-than-15-engines-in-meta-engine/326737>\
**Category:** Elastic Search\
**Tags:** elastic-app-search\
**Created:** [March 1, 2023, 8:25am UTC](https://discuss.elastic.co/t/uploading-more-than-15-engines-in-meta-engine/326737 "2023-03-01T08:25:15Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![mansi\_raval](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mansi_raval/32/117855_2.png) [@mansi\_raval](https://discuss.elastic.co/u/mansi_raval)\
**Post date:** [March 1, 2023, 8:25am UTC](https://discuss.elastic.co/t/uploading-more-than-15-engines-in-meta-engine/326737/1 "2023-03-01T08:25:15Z")

</div>

I have a set of **more than 15 engines** that I've created in elastic app search and I want to **create a meta engine** with them. Is there any way I can **increase the capacity** of the meta engine?

If the capacity can't be increased, then is there a way to **merge indices** that are contained within the engines into **one common index** in order to ensure that the **meta engine** can be **created** without any hassles?

---

<div class="post-metadata">

**Author:** ![Carlos\_D](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/carlos_d/32/126245_2.png) [@Carlos\_D](https://discuss.elastic.co/u/Carlos_D)\
**Post date:** [March 1, 2023, 8:54am UTC](https://discuss.elastic.co/t/uploading-more-than-15-engines-in-meta-engine/326737/2 "2023-03-01T08:54:32Z")

</div>

Hi @mansi_raval , welcome to the community!

Indeed, you can change [configuration](https://www.elastic.co/guide/en/enterprise-search/8.6/configuration.html) to increase the limit of engines per meta engine.

The `app_search.engine.source_engines_per_meta_engine.limit` is the setting you're looking for.

To merge indices, you can use Elasticsearch [Reindex API](https://www.elastic.co/guide/en/elasticsearch/reference/current/docs-reindex.html).

---

<div class="post-metadata">

**Author:** ![mansi\_raval](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mansi_raval/32/117855_2.png) [@mansi\_raval](https://discuss.elastic.co/u/mansi_raval)\
**Post date:** [March 1, 2023, 9:53am UTC](https://discuss.elastic.co/t/uploading-more-than-15-engines-in-meta-engine/326737/3 "2023-03-01T09:53:57Z")

</div>

I read the configuration documentation but I found it to be a bit confusing. Can you please help me out with a step-wise set of instructions to execute the solution you provided ? The specific issue that I'm facing is that when I navigate to the **Elastic Services Console** and then to the **Edit section** I'm only able to view Elasticsearch, Kibana, Integrations Server and Enterprise Search. I can't seem to find App Search. Also when I clicked on "Edit user settings", and copy pasted the following that you suggested (`app_search.engine.source_engines_per_meta_engine.limit`), I received an error as follows `The YAML settings are invalid, please check your syntax`

---

<div class="post-metadata">

**Author:** ![Carlos\_D](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/carlos_d/32/126245_2.png) [@Carlos\_D](https://discuss.elastic.co/u/Carlos_D)\
**Post date:** [March 2, 2023, 8:07am UTC](https://discuss.elastic.co/t/uploading-more-than-15-engines-in-meta-engine/326737/4 "2023-03-02T08:07:17Z")

</div>

Hi @mansi_raval !

App Search is part of Enterprise Search, so that's where you should edit the user settings.

Once you're modifying user settings, pasting the following:

`app_search.engine.source_engines_per_meta_engine.limit=20`

Should set meta engines engine limit to 20.

Keep in mind that you need to save your settings after you close the Edit User settings configuration screen.

Hope this helps!

---

<div class="post-metadata">

**Author:** ![mansi\_raval](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mansi_raval/32/117855_2.png) [@mansi\_raval](https://discuss.elastic.co/u/mansi_raval)\
**Post date:** [March 4, 2023, 6:08am UTC](https://discuss.elastic.co/t/uploading-more-than-15-engines-in-meta-engine/326737/5 "2023-03-04T06:08:39Z")

</div>

I implemented the solution that you provided but I'm getting the same error and I'm unable to view the save option.

After reading the below instructions (the one provided in the user settings console)\* , I read the documentation, however, in this particular instruction - ( 4. In the **Enterprise Search** section, select **Edit user settings**. For deployments with existing user settings, you may have to expand the **Edit enterprise-search.yml** caret instead.) I'm unable to view the Edit enterprise-search.yml option.

\*( Note that the syntax for user settings can change between major versions.  
You might need to update these user settings before performing a major version upgrade.  
To learn more, see the documentation. )

---

<div class="post-metadata">

**Author:** ![Carlos\_D](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/carlos_d/32/126245_2.png) [@Carlos\_D](https://discuss.elastic.co/u/Carlos_D)\
**Post date:** [March 6, 2023, 8:54am UTC](https://discuss.elastic.co/t/uploading-more-than-15-engines-in-meta-engine/326737/6 "2023-03-06T08:54:51Z")

</div>

Hi @mansi_raval :

The following steps should be done for changing user settings:

1. From Edit your deployment, choose Edit User Settings:

 ![Screenshot 2023-03-06 at 09.50.01](https://us1.discourse-cdn.com/elastic/original/3X/6/2/628c2cf49b6aacc5a4adb31cab4cba496eaca07f.png)

1. Change the appropriate user setting, and then click "Back":

 ![Screenshot 2023-03-06 at 09.50.59](https://us1.discourse-cdn.com/elastic/original/3X/8/d/8d5a1b1a2cf01622120c7fb0dd4b26b0c28a79f6.png)

1. Save your changes

 ![Screenshot 2023-03-06 at 09.51.17](https://us1.discourse-cdn.com/elastic/original/3X/2/9/291eb16d1039bca70f3975d659f7c93d4009c093.png)

---

<div class="post-metadata">

**Author:** ![mansi\_raval](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mansi_raval/32/117855_2.png) [@mansi\_raval](https://discuss.elastic.co/u/mansi_raval)\
**Post date:** [March 7, 2023, 6:32am UTC](https://discuss.elastic.co/t/uploading-more-than-15-engines-in-meta-engine/326737/7 "2023-03-07T06:32:42Z")

</div>

This is what is getting displayed when I implement the above steps :

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/e/9/e9be1e493de89de327a70da3ef336e2caf904a50.jpeg)

and when I click on **Back** and **Save** , this is error that is displayed :

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/c/9/c9c543662d41b054f0b588518054b86d496713fc.jpeg)

Could this be due to the version of the enterprise search?

---

<div class="post-metadata">

**Author:** ![Carlos\_D](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/carlos_d/32/126245_2.png) [@Carlos\_D](https://discuss.elastic.co/u/Carlos_D)\
**Post date:** [March 7, 2023, 8:39am UTC](https://discuss.elastic.co/t/uploading-more-than-15-engines-in-meta-engine/326737/8 "2023-03-07T08:39:58Z")

</div>

I think you need to use a space after the colon:

`app_search.engine.source_engines_per_meta_engine.limit: 20`

---

<div class="post-metadata">

**Author:** ![mansi\_raval](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mansi_raval/32/117855_2.png) [@mansi\_raval](https://discuss.elastic.co/u/mansi_raval)\
**Post date:** [March 7, 2023, 9:26am UTC](https://discuss.elastic.co/t/uploading-more-than-15-engines-in-meta-engine/326737/9 "2023-03-07T09:26:51Z")

</div>

Yep! it works now! Thanks a ton 🙂  
That was a basic error from my end...sorry about that.  
Thanks for the help!

---

<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:** [April 4, 2023, 9:27am UTC](https://discuss.elastic.co/t/uploading-more-than-15-engines-in-meta-engine/326737/10 "2023-04-04T09:27:22Z")

</div>

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