# Settings for \_percolator index

**URL:** <https://discuss.elastic.co/t/settings-for--percolator-index/8009>\
**Category:** Elasticsearch\
**Created:** [June 7, 2012, 2:53pm UTC](https://discuss.elastic.co/t/settings-for--percolator-index/8009 "2012-06-07T14:53:09Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![jschelle\_2](https://avatars.discourse-cdn.com/v4/letter/j/f475e1/32.png) [@jschelle\_2](https://discuss.elastic.co/u/jschelle_2)\
**Post date:** [June 7, 2012, 2:53pm UTC](https://discuss.elastic.co/t/settings-for--percolator-index/8009/1 "2012-06-07T14:53:09Z")

</div>

What is the best way to set the settings for the \_percolator index? I  
create an index _benchmark_ and then let elasticsearch create _\_percolator_upon registration of the first query. Should I be manually creating the  
_\_percolator_ index myself so that I can make the settings what I want? Or  
is there a way to store off the settings and have elasticsearch read them  
automatically when it creates the _\_percolator_ index?

---

<div class="post-metadata">

**Author:** ![Clinton\_Gormley](https://avatars.discourse-cdn.com/v4/letter/c/50afbb/32.png) [@Clinton\_Gormley](https://discuss.elastic.co/u/Clinton_Gormley)\
**Post date:** [June 7, 2012, 3:02pm UTC](https://discuss.elastic.co/t/settings-for--percolator-index/8009/2 "2012-06-07T15:02:15Z")

</div>

On Thu, 2012-06-07 at 07:53 -0700, shadow000fire wrote:

> What is the best way to set the settings for the \_percolator index? I  
> create an index benchmark and then let elasticsearch create  
> \_percolator upon registration of the first query. Should I be  
> manually creating the \_percolator index myself so that I can make the  
> settings what I want? Or is there a way to store off the settings and  
> have elasticsearch read them automatically when it creates the  
> \_percolator index?

Easiest is probably just to create the \_percolator index yourself,  
before creating any percolators

clint

---

<div class="post-metadata">

**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\
**Post date:** [June 10, 2012, 9:38pm UTC](https://discuss.elastic.co/t/settings-for--percolator-index/8009/3 "2012-06-10T21:38:21Z")

</div>

What settings are you after?

On Thu, Jun 7, 2012 at 4:53 PM, shadow000fire [jason.scheller@gmail.com](mailto:jason.scheller@gmail.com)wrote:

> What is the best way to set the settings for the \_percolator index? I  
> create an index _benchmark_ and then let elasticsearch create \*\_percolator
> 
> - upon registration of the first query. Should I be manually creating  
> the _\_percolator_ index myself so that I can make the settings what I  
> want? Or is there a way to store off the settings and have elasticsearch  
> read them automatically when it creates the _\_percolator_ index?

---

<div class="post-metadata">

**Author:** ![jschelle\_2](https://avatars.discourse-cdn.com/v4/letter/j/f475e1/32.png) [@jschelle\_2](https://discuss.elastic.co/u/jschelle_2)\
**Post date:** [June 11, 2012, 2:24am UTC](https://discuss.elastic.co/t/settings-for--percolator-index/8009/4 "2012-06-11T02:24:12Z")

</div>

Whatever ones will get me sub 100 ms percolate responses with \>= 100K registered queries.

I think I'm looking for how to distribute percolate requests the way that searches are distributed. But if there's a better approach then I'm looking for that.

Thanks,  
Jay

On Jun 10, 2012, at 5:38 PM, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) wrote:

> What settings are you after?
> 
> On Thu, Jun 7, 2012 at 4:53 PM, shadow000fire [jason.scheller@gmail.com](mailto:jason.scheller@gmail.com) wrote:  
> What is the best way to set the settings for the \_percolator index? I create an index benchmark and then let elasticsearch create \_percolator upon registration of the first query. Should I be manually creating the \_percolator index myself so that I can make the settings what I want? Or is there a way to store off the settings and have elasticsearch read them automatically when it creates the \_percolator index?

---

<div class="post-metadata">

**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\
**Post date:** [June 13, 2012, 5:59pm UTC](https://discuss.elastic.co/t/settings-for--percolator-index/8009/5 "2012-06-13T17:59:03Z")

</div>

You can have several indexes holding parts of the percolated queries, and  
execute them in parallel. Its not amazing, and I hope we address this in  
the upcoming release.

On Mon, Jun 11, 2012 at 4:24 AM, Jason Scheller [jason.scheller@gmail.com](mailto:jason.scheller@gmail.com)wrote:

> Whatever ones will get me sub 100 ms percolate responses with \>= 100K  
> registered queries.
> 
> I think I'm looking for how to distribute percolate requests the way that  
> searches are distributed. But if there's a better approach then I'm looking  
> for that.
> 
> Thanks,  
> Jay
> 
> On Jun 10, 2012, at 5:38 PM, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) wrote:
> 
> What settings are you after?
> 
> On Thu, Jun 7, 2012 at 4:53 PM, shadow000fire [jason.scheller@gmail.com](mailto:jason.scheller@gmail.com)wrote:
> 
> > What is the best way to set the settings for the \_percolator index? I  
> > create an index _benchmark_ and then let elasticsearch create \*  
> > \_percolator\* upon registration of the first query. Should I be manually  
> > creating the _\_percolator_ index myself so that I can make the settings  
> > what I want? Or is there a way to store off the settings and have  
> > elasticsearch read them automatically when it creates the _\_percolator_index?

---

<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 6, 2017, 3:24am UTC](https://discuss.elastic.co/t/settings-for--percolator-index/8009/6 "2017-07-06T03:24:32Z")

</div>

Closed on July 6, 2017, 3:24am UTC


