# Warmer causes slow replication? **URL:** \ **Category:** Elasticsearch\ **Created:** [January 28, 2013, 3:56pm UTC](https://discuss.elastic.co/t/warmer-causes-slow-replication/10525 "2013-01-28T15:56:06Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![James\_Smith](https://avatars.discourse-cdn.com/v4/letter/j/ba9def/32.png) [@James\_Smith](https://discuss.elastic.co/u/James_Smith)\ **Post date:** [January 28, 2013, 3:56pm UTC](https://discuss.elastic.co/t/warmer-causes-slow-replication/10525/1 "2013-01-28T15:56:06Z")
Hi all, Could anyone please tell me if they would expect the presence of a parent / child query warmer to slow replication down greatly? (From ~5 minutes to ~30 minutes for 12gb of data.) It is recommended to disable the warmer before bulk indexing, and I wonder if this applies to replication as well? I believe this is what we are seeing, and if so, it causes us a problem around introducing nodes into a cluster in a live environment, as we must choose between: 1. No warmer -\> very slow first parent / child query 2. Warmer -\> very slow replication Any help would be greatly appreciated! Thanks, James. -- ---
**Author:** ![James\_Smith](https://avatars.discourse-cdn.com/v4/letter/j/ba9def/32.png) [@James\_Smith](https://discuss.elastic.co/u/James_Smith)\ **Post date:** [January 30, 2013, 9:57am UTC](https://discuss.elastic.co/t/warmer-causes-slow-replication/10525/2 "2013-01-30T09:57:33Z")
Just bumping this in the hope that someone may see it and have a suggestion... -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**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:** [January 30, 2013, 11:53am UTC](https://discuss.elastic.co/t/warmer-causes-slow-replication/10525/3 "2013-01-30T11:53:55Z")
Warmers don't slow replication down, replication will take the same time. If you still have the refresh interval to 1 second, then when you index, the warmers will be executed every time the index gets refreshed, which will add more load on the nodes, which will slow down indexing because of the extra load. Thats the main reason why we allow to disable warmers, specifically when doing initial bulk indexing. On Jan 28, 2013, at 4:56 PM, James Smith [jamessm87654@gmail.com](mailto:jamessm87654@gmail.com) wrote: > Hi all, > > Could anyone please tell me if they would expect the presence of a parent / child query warmer to slow replication down greatly? (From ~5 minutes to ~30 minutes for 12gb of data.) > > It is recommended to disable the warmer before bulk indexing, and I wonder if this applies to replication as well? > > I believe this is what we are seeing, and if so, it causes us a problem around introducing nodes into a cluster in a live environment, as we must choose between: > > 1. No warmer -\> very slow first parent / child query > 2. Warmer -\> very slow replication > > Any help would be greatly appreciated! > > Thanks, James. > > -- -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**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, 2:53am UTC](https://discuss.elastic.co/t/warmer-causes-slow-replication/10525/4 "2017-07-06T02:53:57Z")
Closed on July 6, 2017, 2:53am UTC