# Problems expanding replicas for \_percolator **URL:** \ **Category:** Elasticsearch\ **Created:** [February 3, 2012, 4:26pm UTC](https://discuss.elastic.co/t/problems-expanding-replicas-for--percolator/6584 "2012-02-03T16:26:35Z")\ **Posts on this page:** 14\ **Page:** 1
**Author:** ![Kenneth\_Loafman](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kenneth_loafman/32/2224_2.png) [@Kenneth\_Loafman](https://discuss.elastic.co/u/Kenneth_Loafman)\ **Post date:** [February 3, 2012, 4:26pm UTC](https://discuss.elastic.co/t/problems-expanding-replicas-for--percolator/6584/1 "2012-02-03T16:26:35Z")
Hi, I gave up on my previous question about 0-all being answered, but I'm still having troubles with expanding the number of replicas for \_percolator. I'm running 18.6 on 3 nodes, strictly for percolator use. Per the documentation, increasing the number of replicas will increase the number of percolation power, but I'm having trouble getting the number of replicas to increase. I played with the script in the gist below, but the results are the same, every time. The cluster is showing unassigned shards and they never get initialized. Please help. git://gist.github.com/1730911.git ...Thanks, ...Ken ---
**Author:** ![Berkay\_Mollamustafao](https://avatars.discourse-cdn.com/v4/letter/b/22d042/32.png) [@Berkay\_Mollamustafao](https://discuss.elastic.co/u/Berkay_Mollamustafao)\ **Post date:** [February 3, 2012, 7:08pm UTC](https://discuss.elastic.co/t/problems-expanding-replicas-for--percolator/6584/2 "2012-02-03T19:08:51Z")
Gist link below comes up as an empty page at least for me. just fyi.. Regards, Berkay Mollamustafaoglu mberkay on yahoo, google and skype On Fri, Feb 3, 2012 at 11:26 AM, Kenneth Loafman [kenneth.loafman@gmail.com](mailto:kenneth.loafman@gmail.com)wrote: > Hi, > > I gave up on my previous question about 0-all being answered, but I'm > still having troubles with expanding the number of replicas for \_percolator. > > I'm running 18.6 on 3 nodes, strictly for percolator use. Per the > documentation, > > increasing the number of replicas will increase the number of percolation > power, > > but I'm having trouble getting the number of replicas to increase. I > played with the script in the gist below, but the results are the same, > every time. The cluster is showing unassigned shards and they never get > initialized. Please help. > > git://gist.github.com/1730911.git > > ...Thanks, > ...Ken ---
**Author:** ![Kenneth\_Loafman\_2](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kenneth_loafman_2/32/2224_2.png) [@Kenneth\_Loafman\_2](https://discuss.elastic.co/u/Kenneth_Loafman_2)\ **Post date:** [February 3, 2012, 7:29pm UTC](https://discuss.elastic.co/t/problems-expanding-replicas-for--percolator/6584/3 "2012-02-03T19:29:21Z")
Sorry, I posted the public git repo link. Try this > ...Ken On Fri, Feb 3, 2012 at 1:08 PM, Berkay Mollamustafaoglu [mberkay@gmail.com](mailto:mberkay@gmail.com)wrote: > Gist link below comes up as an empty page at least for me. just fyi.. > > Regards, > Berkay Mollamustafaoglu > mberkay on yahoo, google and skype > > On Fri, Feb 3, 2012 at 11:26 AM, Kenneth Loafman \< > [kenneth.loafman@gmail.com](mailto:kenneth.loafman@gmail.com)\> wrote: > > > Hi, > > > > I gave up on my previous question about 0-all being answered, but I'm > > still having troubles with expanding the number of replicas for \_percolator. > > > > I'm running 18.6 on 3 nodes, strictly for percolator use. Per the > > documentation, > > > > increasing the number of replicas will increase the number of percolation > > power, > > > > but I'm having trouble getting the number of replicas to increase. I > > played with the script in the gist below, but the results are the same, > > every time. The cluster is showing unassigned shards and they never get > > initialized. Please help. > > > > git://gist.github.com/1730911.git > > > > ...Thanks, > > ...Ken ---
**Author:** ![Kenneth\_Loafman](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kenneth_loafman/32/2224_2.png) [@Kenneth\_Loafman](https://discuss.elastic.co/u/Kenneth_Loafman)\ **Post date:** [February 3, 2012, 11:56pm UTC](https://discuss.elastic.co/t/problems-expanding-replicas-for--percolator/6584/4 "2012-02-03T23:56:52Z")
Sorry, I posted the public git repo link. Try this > ...Ken On Fri, Feb 3, 2012 at 1:29 PM, Kenneth Loafman [kenneth@loafman.com](mailto:kenneth@loafman.com) wrote: > Sorry, I posted the public git repo link. Try this > [Problem expanding replicas for \_percolator · GitHub](https://gist.github.com/1730911) > > ...Ken > > On Fri, Feb 3, 2012 at 1:08 PM, Berkay Mollamustafaoglu \<[mberkay@gmail.com](mailto:mberkay@gmail.com) > > > wrote: > > > Gist link below comes up as an empty page at least for me. just fyi.. > > > > Regards, > > Berkay Mollamustafaoglu > > mberkay on yahoo, google and skype > > > > On Fri, Feb 3, 2012 at 11:26 AM, Kenneth Loafman \< > > [kenneth.loafman@gmail.com](mailto:kenneth.loafman@gmail.com)\> wrote: > > > > > Hi, > > > > > > I gave up on my previous question about 0-all being answered, but I'm > > > still having troubles with expanding the number of replicas for \_percolator. > > > > > > I'm running 18.6 on 3 nodes, strictly for percolator use. Per the > > > documentation, > > > > > > increasing the number of replicas will increase the number of > > > percolation power, > > > > > > but I'm having trouble getting the number of replicas to increase. I > > > played with the script in the gist below, but the results are the same, > > > every time. The cluster is showing unassigned shards and they never get > > > initialized. Please help. > > > > > > git://gist.github.com/1730911.git > > > > > > ...Thanks, > > > ...Ken ---
**Author:** ![Berkay\_Mollamustafao](https://avatars.discourse-cdn.com/v4/letter/b/22d042/32.png) [@Berkay\_Mollamustafao](https://discuss.elastic.co/u/Berkay_Mollamustafao)\ **Post date:** [February 4, 2012, 1:16am UTC](https://discuss.elastic.co/t/problems-expanding-replicas-for--percolator/6584/5 "2012-02-04T01:16:14Z")
ES does not put 2 copies of the same shard on the same node. You have 3 nodes so you can currently have max 2 replicas. It's probably why your cluster status is yellow as well. On Friday, February 3, 2012, Kenneth Loafman [kenneth@loafman.com](mailto:kenneth@loafman.com) wrote: > Sorry, I posted the public git repo link. Try this > [Problem expanding replicas for \_percolator · GitHub](https://gist.github.com/1730911) > ...Ken > > On Fri, Feb 3, 2012 at 1:08 PM, Berkay Mollamustafaoglu [mberkay@gmail.com](mailto:mberkay@gmail.com) > wrote: > > > Gist link below comes up as an empty page at least for me. just fyi.. > > Regards, > > Berkay Mollamustafaoglu > > mberkay on yahoo, google and skype > > > > On Fri, Feb 3, 2012 at 11:26 AM, Kenneth Loafman \< > > [kenneth.loafman@gmail.com](mailto:kenneth.loafman@gmail.com)\> wrote: > > > > > Hi, > > > I gave up on my previous question about 0-all being answered, but I'm > > > still having troubles with expanding the number of replicas for \_percolator. > > > I'm running 18.6 on 3 nodes, strictly for percolator use. Per the > > > documentation, > > > increasing the number of replicas will increase the number of > > > percolation power, > > > but I'm having trouble getting the number of replicas to increase. I > > > played with the script in the gist below, but the results are the same, > > > every time. The cluster is showing unassigned shards and they never get > > > initialized. Please help. > > > git://gist.github.com/1730911.git > > > ...Thanks, > > > ...Ken -- Regards, Berkay Mollamustafaoglu Ph: +1 (571) 766-6292 mberkay on yahoo, google and skype ---
**Author:** ![Kenneth\_Loafman\_2](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kenneth_loafman_2/32/2224_2.png) [@Kenneth\_Loafman\_2](https://discuss.elastic.co/u/Kenneth_Loafman_2)\ **Post date:** [February 4, 2012, 2:27am UTC](https://discuss.elastic.co/t/problems-expanding-replicas-for--percolator/6584/6 "2012-02-04T02:27:21Z")
So how do you get more replicas? Should I run another node on each machine? On Fri, Feb 3, 2012 at 7:16 PM, Berkay Mollamustafaoglu [mberkay@gmail.com](mailto:mberkay@gmail.com)wrote: > ES does not put 2 copies of the same shard on the same node. You have 3 > nodes so you can currently have max 2 replicas. It's probably why your > cluster status is yellow as well. > > On Friday, February 3, 2012, Kenneth Loafman [kenneth@loafman.com](mailto:kenneth@loafman.com) wrote: > > > Sorry, I posted the public git repo link. Try this > > [Problem expanding replicas for \_percolator · GitHub](https://gist.github.com/1730911) > > ...Ken > > > > On Fri, Feb 3, 2012 at 1:08 PM, Berkay Mollamustafaoglu \< > > [mberkay@gmail.com](mailto:mberkay@gmail.com)\> wrote: > > > > > Gist link below comes up as an empty page at least for me. just fyi.. > > > Regards, > > > Berkay Mollamustafaoglu > > > mberkay on yahoo, google and skype > > > > > > On Fri, Feb 3, 2012 at 11:26 AM, Kenneth Loafman \< > > > [kenneth.loafman@gmail.com](mailto:kenneth.loafman@gmail.com)\> wrote: > > > > > > > Hi, > > > > I gave up on my previous question about 0-all being answered, but I'm > > > > still having troubles with expanding the number of replicas for \_percolator. > > > > I'm running 18.6 on 3 nodes, strictly for percolator use. Per the > > > > documentation, > > > > increasing the number of replicas will increase the number of > > > > percolation power, > > > > but I'm having trouble getting the number of replicas to increase. I > > > > played with the script in the gist below, but the results are the same, > > > > every time. The cluster is showing unassigned shards and they never get > > > > initialized. Please help. > > > > git://gist.github.com/1730911.git > > > > ...Thanks, > > > > ...Ken > > -- > Regards, > Berkay Mollamustafaoglu > Ph: +1 (571) 766-6292 > > mberkay on yahoo, google and skype ---
**Author:** ![Kenneth\_Loafman](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kenneth_loafman/32/2224_2.png) [@Kenneth\_Loafman](https://discuss.elastic.co/u/Kenneth_Loafman)\ **Post date:** [February 4, 2012, 5:30pm UTC](https://discuss.elastic.co/t/problems-expanding-replicas-for--percolator/6584/7 "2012-02-04T17:30:53Z")
Thanks. I did not understand that limitation. I solved the problem by adding a 2nd node to each machine to get more percolators (now a 6-node cluster). That lowered the average time per percolate, so problem is solved, for now. ...Ken On Fri, Feb 3, 2012 at 7:16 PM, Berkay Mollamustafaoglu [mberkay@gmail.com](mailto:mberkay@gmail.com)wrote: > ES does not put 2 copies of the same shard on the same node. You have 3 > nodes so you can currently have max 2 replicas. It's probably why your > cluster status is yellow as well. > > On Friday, February 3, 2012, Kenneth Loafman [kenneth@loafman.com](mailto:kenneth@loafman.com) wrote: > > > Sorry, I posted the public git repo link. Try this > > [Problem expanding replicas for \_percolator · GitHub](https://gist.github.com/1730911) > > ...Ken > > > > On Fri, Feb 3, 2012 at 1:08 PM, Berkay Mollamustafaoglu \< > > [mberkay@gmail.com](mailto:mberkay@gmail.com)\> wrote: > > > > > Gist link below comes up as an empty page at least for me. just fyi.. > > > Regards, > > > Berkay Mollamustafaoglu > > > mberkay on yahoo, google and skype > > > > > > On Fri, Feb 3, 2012 at 11:26 AM, Kenneth Loafman \< > > > [kenneth.loafman@gmail.com](mailto:kenneth.loafman@gmail.com)\> wrote: > > > > > > > Hi, > > > > I gave up on my previous question about 0-all being answered, but I'm > > > > still having troubles with expanding the number of replicas for \_percolator. > > > > I'm running 18.6 on 3 nodes, strictly for percolator use. Per the > > > > documentation, > > > > increasing the number of replicas will increase the number of > > > > percolation power, > > > > but I'm having trouble getting the number of replicas to increase. I > > > > played with the script in the gist below, but the results are the same, > > > > every time. The cluster is showing unassigned shards and they never get > > > > initialized. Please help. > > > > git://gist.github.com/1730911.git > > > > ...Thanks, > > > > ...Ken > > -- > Regards, > Berkay Mollamustafaoglu > Ph: +1 (571) 766-6292 > > mberkay on yahoo, google and skype ---
**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:** [February 5, 2012, 5:11pm UTC](https://discuss.elastic.co/t/problems-expanding-replicas-for--percolator/6584/8 "2012-02-05T17:11:24Z")
The comment is meant to say that increasing the number of replicas for the actual index (not \_percoalte, which just acts as the storage to the registered queries) will increase percolation performance. The \_percolate index should not change, and should always be 1 shard with 0-all replicas (so it will be spread across the nodes storage wise, and all nodes will be able to read the queries registered). On Friday, February 3, 2012 at 6:26 PM, Kenneth Loafman wrote: > Hi, > > I gave up on my previous question about 0-all being answered, but I'm still having troubles with expanding the number of replicas for \_percolator. > > I'm running 18.6 on 3 nodes, strictly for percolator use. Per the documentation, > > increasing the number of replicas will increase the number of percolation power, > > but I'm having trouble getting the number of replicas to increase. I played with the script in the gist below, but the results are the same, every time. The cluster is showing unassigned shards and they never get initialized. Please help. > > git://gist.github.com/1730911.git ([Problem expanding replicas for \_percolator · GitHub](http://gist.github.com/1730911.git)) > > ...Thanks, > ...Ken ---
**Author:** ![Kenneth\_Loafman\_2](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kenneth_loafman_2/32/2224_2.png) [@Kenneth\_Loafman\_2](https://discuss.elastic.co/u/Kenneth_Loafman_2)\ **Post date:** [February 5, 2012, 5:19pm UTC](https://discuss.elastic.co/t/problems-expanding-replicas-for--percolator/6584/9 "2012-02-05T17:19:46Z")
As it turns out the indexes are fake ('filters' and 'excludes') with the same mapping as the other indexes and these reside on the percolator cluster, so my solution worked, but for a different reason than I thought. They are also 1 shard, 0-all replicas. So I guess the only way to increase the number of filters and excludes indexes is to add nodes, if I understand correctly? On Sun, Feb 5, 2012 at 11:11 AM, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) wrote: > The comment is meant to say that increasing the number of replicas for > the actual index (not \_percoalte, which just acts as the storage to the > registered queries) will increase percolation performance. The \_percolate > index should not change, and should always be 1 shard with 0-all replicas > (so it will be spread across the nodes storage wise, and all nodes will be > able to read the queries registered). > > On Friday, February 3, 2012 at 6:26 PM, Kenneth Loafman wrote: > > Hi, > > I gave up on my previous question about 0-all being answered, but I'm > still having troubles with expanding the number of replicas for \_percolator. > > I'm running 18.6 on 3 nodes, strictly for percolator use. Per the > documentation, > > increasing the number of replicas will increase the number of percolation > power, > > but I'm having trouble getting the number of replicas to increase. I > played with the script in the gist below, but the results are the same, > every time. The cluster is showing unassigned shards and they never get > initialized. Please help. > > git://gist.github.com/1730911.git > > ...Thanks, > ...Ken ---
**Author:** ![Kenneth\_Loafman](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kenneth_loafman/32/2224_2.png) [@Kenneth\_Loafman](https://discuss.elastic.co/u/Kenneth_Loafman)\ **Post date:** [February 5, 2012, 5:22pm UTC](https://discuss.elastic.co/t/problems-expanding-replicas-for--percolator/6584/10 "2012-02-05T17:22:29Z")
As it turns out the indexes are fake ('filters' and 'excludes') with the same mapping as the other indexes and these reside on the percolator cluster, so my solution worked, but for a different reason than I thought. They are also 1 shard, 0-all replicas. So I guess the only way to increase the number of filters and excludes indexes is to add nodes, if I understand correctly? On Sun, Feb 5, 2012 at 11:11 AM, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) wrote: > The comment is meant to say that increasing the number of replicas for > the actual index (not \_percoalte, which just acts as the storage to the > registered queries) will increase percolation performance. The \_percolate > index should not change, and should always be 1 shard with 0-all replicas > (so it will be spread across the nodes storage wise, and all nodes will be > able to read the queries registered). > > On Friday, February 3, 2012 at 6:26 PM, Kenneth Loafman wrote: > > Hi, > > I gave up on my previous question about 0-all being answered, but I'm > still having troubles with expanding the number of replicas for \_percolator. > > I'm running 18.6 on 3 nodes, strictly for percolator use. Per the > documentation, > > increasing the number of replicas will increase the number of percolation > power, > > but I'm having trouble getting the number of replicas to increase. I > played with the script in the gist below, but the results are the same, > every time. The cluster is showing unassigned shards and they never get > initialized. Please help. > > git://gist.github.com/1730911.git > > ...Thanks, > ...Ken ---
**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:** [February 5, 2012, 5:38pm UTC](https://discuss.elastic.co/t/problems-expanding-replicas-for--percolator/6584/11 "2012-02-05T17:38:39Z")
What do you mean by fake indices? You mean they hold no data except for percolating against them? Thats fine, they are still your "compute" power for percolation (and sometimes, they also hold data). Note, once a shard for an index (not the \_percolate index, the one you register the query against) exists on a node, then it will make use of that node. The percolation action can be executed concurrently on the same shard. And yes, adding more nodes will mean better performance. With percolation, if you have "fake" indices as you mentioned, then its good enough to have a single shard of those fake indices, and 0-all for the replicas. This will mean that automatically, as you add nodes, those replicas will expand to make use of the new node, and will also service percolation requests. Still, not to be confused with the \_percolate index, which only acts as persistent storage for the percolated queries, and needs to be 0-all so it will exists on all nodes. On Sunday, February 5, 2012 at 7:22 PM, Kenneth Loafman wrote: > As it turns out the indexes are fake ('filters' and 'excludes') with the same mapping as the other indexes and these reside on the percolator cluster, so my solution worked, but for a different reason than I thought. They are also 1 shard, 0-all replicas. So I guess the only way to increase the number of filters and excludes indexes is to add nodes, if I understand correctly? > > On Sun, Feb 5, 2012 at 11:11 AM, Shay Banon \<[kimchy@gmail.com](mailto:kimchy@gmail.com) ([mailto:kimchy@gmail.com](mailto:kimchy@gmail.com))\> wrote: > > > The comment is meant to say that increasing the number of replicas for the actual index (not \_percoalte, which just acts as the storage to the registered queries) will increase percolation performance. The \_percolate index should not change, and should always be 1 shard with 0-all replicas (so it will be spread across the nodes storage wise, and all nodes will be able to read the queries registered). > > > > On Friday, February 3, 2012 at 6:26 PM, Kenneth Loafman wrote: > > > > > Hi, > > > > > > I gave up on my previous question about 0-all being answered, but I'm still having troubles with expanding the number of replicas for \_percolator. > > > > > > I'm running 18.6 on 3 nodes, strictly for percolator use. Per the documentation, > > > > > > increasing the number of replicas will increase the number of percolation power, > > > > > > but I'm having trouble getting the number of replicas to increase. I played with the script in the gist below, but the results are the same, every time. The cluster is showing unassigned shards and they never get initialized. Please help. > > > > > > git://gist.github.com/1730911.git ([Problem expanding replicas for \_percolator · GitHub](http://gist.github.com/1730911.git)) > > > > > > ...Thanks, > > > ...Ken ---
**Author:** ![Kenneth\_Loafman\_2](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kenneth_loafman_2/32/2224_2.png) [@Kenneth\_Loafman\_2](https://discuss.elastic.co/u/Kenneth_Loafman_2)\ **Post date:** [February 5, 2012, 6:45pm UTC](https://discuss.elastic.co/t/problems-expanding-replicas-for--percolator/6584/12 "2012-02-05T18:45:10Z")
Yes, the fake indexes contain no data. I add an extra field to each filter which give me information on what matched and where to store it. That works out well for a multi-tenant operation where there may be overlap in the filters. On Sun, Feb 5, 2012 at 11:38 AM, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) wrote: > What do you mean by fake indices? You mean they hold no data except for > percolating against them? Thats fine, they are still your "compute" power > for percolation (and sometimes, they also hold data). > > Note, once a shard for an index (not the \_percolate index, the one you > register the query against) exists on a node, then it will make use of that > node. The percolation action can be executed concurrently on the same > shard. And yes, adding more nodes will mean better performance. > > With percolation, if you have "fake" indices as you mentioned, then its > good enough to have a single shard of those fake indices, and 0-all for the > replicas. This will mean that automatically, as you add nodes, those > replicas will expand to make use of the new node, and will also service > percolation requests. > > Still, not to be confused with the \_percolate index, which only acts as > persistent storage for the percolated queries, and needs to be 0-all so it > will exists on all nodes. > > On Sunday, February 5, 2012 at 7:22 PM, Kenneth Loafman wrote: > > As it turns out the indexes are fake ('filters' and 'excludes') with the > same mapping as the other indexes and these reside on the percolator > cluster, so my solution worked, but for a different reason than I thought. > They are also 1 shard, 0-all replicas. So I guess the only way to > increase the number of filters and excludes indexes is to add nodes, if I > understand correctly? > > On Sun, Feb 5, 2012 at 11:11 AM, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) wrote: > > The comment is meant to say that increasing the number of replicas for > the actual index (not \_percoalte, which just acts as the storage to the > registered queries) will increase percolation performance. The \_percolate > index should not change, and should always be 1 shard with 0-all replicas > (so it will be spread across the nodes storage wise, and all nodes will be > able to read the queries registered). > > On Friday, February 3, 2012 at 6:26 PM, Kenneth Loafman wrote: > > Hi, > > I gave up on my previous question about 0-all being answered, but I'm > still having troubles with expanding the number of replicas for \_percolator. > > I'm running 18.6 on 3 nodes, strictly for percolator use. Per the > documentation, > > increasing the number of replicas will increase the number of percolation > power, > > but I'm having trouble getting the number of replicas to increase. I > played with the script in the gist below, but the results are the same, > every time. The cluster is showing unassigned shards and they never get > initialized. Please help. > > git://gist.github.com/1730911.git > > ...Thanks, > ...Ken ---
**Author:** ![Kenneth\_Loafman](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kenneth_loafman/32/2224_2.png) [@Kenneth\_Loafman](https://discuss.elastic.co/u/Kenneth_Loafman)\ **Post date:** [February 5, 2012, 6:45pm UTC](https://discuss.elastic.co/t/problems-expanding-replicas-for--percolator/6584/13 "2012-02-05T18:45:53Z")
Yes, the fake indexes contain no data. I add an extra field to each filter which give me information on what matched and where to store it. That works out well for a multi-tenant operation where there may be overlap in the filters. On Sun, Feb 5, 2012 at 11:38 AM, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) wrote: > What do you mean by fake indices? You mean they hold no data except for > percolating against them? Thats fine, they are still your "compute" power > for percolation (and sometimes, they also hold data). > > Note, once a shard for an index (not the \_percolate index, the one you > register the query against) exists on a node, then it will make use of that > node. The percolation action can be executed concurrently on the same > shard. And yes, adding more nodes will mean better performance. > > With percolation, if you have "fake" indices as you mentioned, then its > good enough to have a single shard of those fake indices, and 0-all for the > replicas. This will mean that automatically, as you add nodes, those > replicas will expand to make use of the new node, and will also service > percolation requests. > > Still, not to be confused with the \_percolate index, which only acts as > persistent storage for the percolated queries, and needs to be 0-all so it > will exists on all nodes. > > On Sunday, February 5, 2012 at 7:22 PM, Kenneth Loafman wrote: > > As it turns out the indexes are fake ('filters' and 'excludes') with the > same mapping as the other indexes and these reside on the percolator > cluster, so my solution worked, but for a different reason than I thought. > They are also 1 shard, 0-all replicas. So I guess the only way to > increase the number of filters and excludes indexes is to add nodes, if I > understand correctly? > > On Sun, Feb 5, 2012 at 11:11 AM, Shay Banon [kimchy@gmail.com](mailto:kimchy@gmail.com) wrote: > > The comment is meant to say that increasing the number of replicas for > the actual index (not \_percoalte, which just acts as the storage to the > registered queries) will increase percolation performance. The \_percolate > index should not change, and should always be 1 shard with 0-all replicas > (so it will be spread across the nodes storage wise, and all nodes will be > able to read the queries registered). > > On Friday, February 3, 2012 at 6:26 PM, Kenneth Loafman wrote: > > Hi, > > I gave up on my previous question about 0-all being answered, but I'm > still having troubles with expanding the number of replicas for \_percolator. > > I'm running 18.6 on 3 nodes, strictly for percolator use. Per the > documentation, > > increasing the number of replicas will increase the number of percolation > power, > > but I'm having trouble getting the number of replicas to increase. I > played with the script in the gist below, but the results are the same, > every time. The cluster is showing unassigned shards and they never get > initialized. Please help. > > git://gist.github.com/1730911.git > > ...Thanks, > ...Ken ---
**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:40am UTC](https://discuss.elastic.co/t/problems-expanding-replicas-for--percolator/6584/14 "2017-07-06T03:40:31Z")