# When use curator to manager es 5.4.3 how setting put\_mapping time\_out **URL:** \ **Category:** Elasticsearch\ **Created:** [October 19, 2017, 3:19am UTC](https://discuss.elastic.co/t/when-use-curator-to-manager-es-5-4-3-how-setting-put-mapping-time-out/104481 "2017-10-19T03:19:41Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![zqc0512](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zqc0512/32/32141_2.png) [@zqc0512](https://discuss.elastic.co/u/zqc0512)\ **Post date:** [October 19, 2017, 3:19am UTC](https://discuss.elastic.co/t/when-use-curator-to-manager-es-5-4-3-how-setting-put-mapping-time-out/104481/1 "2017-10-19T03:19:41Z")
when use curator to manager es i find there is have timeout setting about curator post commad as flow i change the time\_out can delete indices: DELETE [http://hostname:9200/system-log-61-2017.08,system-log-61-2017.09,system-log-61-2017.10](http://hostname:9200/system-log-61-2017.08,system-log-61-2017.09,system-log-61-2017.10)? **master\_timeout=300s** [status:200 request:4.370s] this time out can setting about put\_mapping timeout the default put\_mapping timeout is 30s but when a large cluster the time is small , how can change the put\_mapping default timeout thanks. error as `Preformatted text[2017-10-19T00:01:21,440][DEBUG][o.e.a.a.i.m.p.TransportPutMappingAction] [hostname] failed to put mappings on indic`` s [[[indicesname/xxxxxx]]], type [tepmlate\_name] org.elasticsearch.cluster.metadata.ProcessClusterEventTimeoutException: failed to process cluster **event (put-mapping) within 30s** at org.elasticsearch.cluster.service.ClusterService.lambda$onTimeout$4(ClusterService.java:497) ~[elasticsearch-5.3.0.jar: 5.3.0] at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:544) [elasticse arch-5.3.0.jar:5.3.0] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:1.8.0\_121] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:1.8.0\_121] at java.lang.Thread.run(Thread.java:745) [?:1.8.0\_121] ---
**Author:** ![theuntergeek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/theuntergeek/32/44961_2.png) [@theuntergeek](https://discuss.elastic.co/u/theuntergeek)\ **Post date:** [October 19, 2017, 7:52am UTC](https://discuss.elastic.co/t/when-use-curator-to-manager-es-5-4-3-how-setting-put-mapping-time-out/104481/2 "2017-10-19T07:52:59Z")
There's two different timeouts in play here. One is the client timeout, as defined in your client configuration YAML file, and the other is a `master_timeout`, which defaults to 30 seconds, but Curator only overrides for the `delete_indices` action. > [@zqc0512](#): > > i find there is have timeout setting about curator post commad as flow i change the time\_out can delete indices: > > DELETE [http://hostname:9200/system-log-61-2017.08,system-log-61-2017.09,system-log-61-2017.10?master\_timeout=300s](http://hostname:9200/system-log-61-2017.08,system-log-61-2017.09,system-log-61-2017.10?master_timeout=300s) [status:200 request:4.370s] The above indicates that the `master_timeout` has been increased for the `delete_indices` action. In spite of this increase, the delete indices request has only actually taken 4.37 seconds. Again, the `master_timeout` change is something Curator does for you, if you are doing the `delete_indices` action. `failed to process cluster event (put-mapping) within 30s` indicates that your cluster cannot process your put mapping request within 30 seconds, regardless of what the client timeout has been set to. I presume you're using something else, as Curator doesn't do mapping requests right now. You may be able to add `master_timeout=300s` to the end of your request, as that flag works on many different API calls. ---
**Author:** ![zqc0512](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zqc0512/32/32141_2.png) [@zqc0512](https://discuss.elastic.co/u/zqc0512)\ **Post date:** [October 19, 2017, 8:33am UTC](https://discuss.elastic.co/t/when-use-curator-to-manager-es-5-4-3-how-setting-put-mapping-time-out/104481/3 "2017-10-19T08:33:21Z")
yes i know about how to add the master\_timeout, bu i don't know how to change the **failed to process cluster event (put-mapping) within 30s** whe in a large cluster the time is small the put\_mapping is use **\_template** auto add when i create index. this seeting is add on the curl put ? i add **master\_timeout** in **bulk**? ---
**Author:** ![theuntergeek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/theuntergeek/32/44961_2.png) [@theuntergeek](https://discuss.elastic.co/u/theuntergeek)\ **Post date:** [October 19, 2017, 8:59am UTC](https://discuss.elastic.co/t/when-use-curator-to-manager-es-5-4-3-how-setting-put-mapping-time-out/104481/4 "2017-10-19T08:59:07Z")
That should be possible, though I've never personally done it. It's the only thing that will help, other than changing the volume of your bulk request to be smaller, or even individual. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [November 16, 2017, 9:07am UTC](https://discuss.elastic.co/t/when-use-curator-to-manager-es-5-4-3-how-setting-put-mapping-time-out/104481/5 "2017-11-16T09:07:55Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.