# ProcessClusterEventTimeoutException in Elasticsearch. Is this timeout value configurable? If yes how? **URL:** \ **Category:** Elasticsearch\ **Created:** [January 28, 2014, 9:08pm UTC](https://discuss.elastic.co/t/processclustereventtimeoutexception-in-elasticsearch-is-this-timeout-value-configurable-if-yes-how/15458 "2014-01-28T21:08:49Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![Munna](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/munna/32/1841_2.png) [@Munna](https://discuss.elastic.co/u/Munna)\ **Post date:** [January 28, 2014, 9:08pm UTC](https://discuss.elastic.co/t/processclustereventtimeoutexception-in-elasticsearch-is-this-timeout-value-configurable-if-yes-how/15458/1 "2014-01-28T21:08:49Z")
Getting timeout exceptions like below for different index operations. Below one shows for "index-aliases" operation. I would like to know how can I configure this timeout value in elasticsearch.yml so that I configure it once and I do not have to worry about this timeout exception. org.elasticsearch.cluster.metadata.ProcessClusterEventTimeoutException: failed to process cluster event (index-aliases) within 30s at org.elasticsearch.cluster.service.InternalClusterService$2$1.run(InternalClusterService.java:237) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) I saw in elasticsearch code that public abstract class MasterNodeOperationRequest extends ActionRequest { ``` public static TimeValue DEFAULT_MASTER_NODE_TIMEOUT = ``` TimeValue.timeValueSeconds(30); ``` protected TimeValue masterNodeTimeout = DEFAULT_MASTER_NODE_TIMEOUT; ``` Thanks, Munna -- 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). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/8ee9ef0f-e1f2-4230-a7cf-1dfec4eee9b7%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/8ee9ef0f-e1f2-4230-a7cf-1dfec4eee9b7%40googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Ivan](https://avatars.discourse-cdn.com/v4/letter/i/df788c/32.png) [@Ivan](https://discuss.elastic.co/u/Ivan)\ **Post date:** [January 29, 2014, 5:32pm UTC](https://discuss.elastic.co/t/processclustereventtimeoutexception-in-elasticsearch-is-this-timeout-value-configurable-if-yes-how/15458/2 "2014-01-29T17:32:07Z")
It appears that this value is not configurable. IMHO, it should be, so perhaps you should open an issue on Github and see if the elasticsearch team agrees. Better yet, submit a pull request. 🙂 -- Ivan On Tue, Jan 28, 2014 at 1:08 PM, Ahaduzzaman Munna \< [ahaduzzaman.munna@gmail.com](mailto:ahaduzzaman.munna@gmail.com)\> wrote: > Getting timeout exceptions like below for different index operations. > Below one shows for "index-aliases" operation. I would like to know how > can I configure this timeout value in elasticsearch.yml so that I configure > it once and I do not have to worry about this timeout exception. > > org.elasticsearch.cluster.metadata.ProcessClusterEventTimeoutException: > failed to process cluster event (index-aliases) within 30s > at > org.elasticsearch.cluster.service.InternalClusterService$2$1.run(InternalClusterService.java:237) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:744) > > I saw in elasticsearch code that > > public abstract class MasterNodeOperationRequest extends ActionRequest { > > ``` > public static TimeValue DEFAULT_MASTER_NODE_TIMEOUT = > > ``` > > TimeValue.timeValueSeconds(30); > > ``` > protected TimeValue masterNodeTimeout = DEFAULT_MASTER_NODE_TIMEOUT; > > ``` > > Thanks, > Munna > > -- > 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). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/8ee9ef0f-e1f2-4230-a7cf-1dfec4eee9b7%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/8ee9ef0f-e1f2-4230-a7cf-1dfec4eee9b7%40googlegroups.com) > . > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- 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). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CALY%3DcQBs78QWDyaKcL71Spd3775HRT3EN1MZnhn0GakfDkwvSA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CALY%3DcQBs78QWDyaKcL71Spd3775HRT3EN1MZnhn0GakfDkwvSA%40mail.gmail.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![javanna](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/javanna/32/4698_2.png) [@javanna](https://discuss.elastic.co/u/javanna)\ **Post date:** [January 29, 2014, 6:07pm UTC](https://discuss.elastic.co/t/processclustereventtimeoutexception-in-elasticsearch-is-this-timeout-value-configurable-if-yes-how/15458/3 "2014-01-29T18:07:50Z")
The master node timeout is configurable on each call using the master\_timeout parameter. There's no global default exposed as settings though. Cheers Luca On Wednesday, January 29, 2014 6:32:07 PM UTC+1, Ivan Brusic wrote: > It appears that this value is not configurable. IMHO, it should be, so > perhaps you should open an issue on Github and see if the elasticsearch > team agrees. Better yet, submit a pull request. 🙂 > > -- > Ivan > > On Tue, Jan 28, 2014 at 1:08 PM, Ahaduzzaman Munna \<[ahaduzza...@gmail.com](mailto:ahaduzza...@gmail.com)\ > > > wrote: > > > Getting timeout exceptions like below for different index operations. > > Below one shows for "index-aliases" operation. I would like to know how > > can I configure this timeout value in elasticsearch.yml so that I configure > > it once and I do not have to worry about this timeout exception. > > > > org.elasticsearch.cluster.metadata.ProcessClusterEventTimeoutException: > > failed to process cluster event (index-aliases) within 30s > > at > > org.elasticsearch.cluster.service.InternalClusterService$2$1.run(InternalClusterService.java:237) > > at > > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > > at > > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > > at java.lang.Thread.run(Thread.java:744) > > > > I saw in elasticsearch code that > > > > public abstract class MasterNodeOperationRequest extends ActionRequest { > > > > ``` > > public static TimeValue DEFAULT_MASTER_NODE_TIMEOUT = > > > > ``` > > > > TimeValue.timeValueSeconds(30); > > > > ``` > > protected TimeValue masterNodeTimeout = DEFAULT_MASTER_NODE_TIMEOUT; > > > > ``` > > > > Thanks, > > Munna > > > > -- > > 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 [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \. > > To view this discussion on the web visit > > [https://groups.google.com/d/msgid/elasticsearch/8ee9ef0f-e1f2-4230-a7cf-1dfec4eee9b7%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/8ee9ef0f-e1f2-4230-a7cf-1dfec4eee9b7%40googlegroups.com) > > . > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- 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). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/9a0bd096-ce5d-4f2e-9f2d-9c5c34fd374b%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/9a0bd096-ce5d-4f2e-9f2d-9c5c34fd374b%40googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Munna](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/munna/32/1841_2.png) [@Munna](https://discuss.elastic.co/u/Munna)\ **Post date:** [January 29, 2014, 8:26pm UTC](https://discuss.elastic.co/t/processclustereventtimeoutexception-in-elasticsearch-is-this-timeout-value-configurable-if-yes-how/15458/4 "2014-01-29T20:26:53Z")
Yes, I feel its little inconvenient not to have that default value configurable via the config file or an API. I hope ES team do something about it. I didn't want to touch my code rather I wanted to have some global configurable setting to make my life easy .... On Wed, Jan 29, 2014 at 12:07 PM, Luca Cavanna [cavannaluca@gmail.com](mailto:cavannaluca@gmail.com)wrote: > The master node timeout is configurable on each call using the > master\_timeout parameter. There's no global default exposed as settings > though. > > Cheers > Luca > > On Wednesday, January 29, 2014 6:32:07 PM UTC+1, Ivan Brusic wrote: > > > It appears that this value is not configurable. IMHO, it should be, so > > perhaps you should open an issue on Github and see if the elasticsearch > > team agrees. Better yet, submit a pull request. 🙂 > > > > -- > > Ivan > > > > On Tue, Jan 28, 2014 at 1:08 PM, Ahaduzzaman Munna \<[ahaduzza...@gmail.com](mailto:ahaduzza...@gmail.com) > > > > > wrote: > > > > > Getting timeout exceptions like below for different index operations. > > > Below one shows for "index-aliases" operation. I would like to know how > > > can I configure this timeout value in elasticsearch.yml so that I configure > > > it once and I do not have to worry about this timeout exception. > > > > > > org.elasticsearch.cluster.metadata.ProcessClusterEventTimeoutException: > > > failed to process cluster event (index-aliases) within 30s > > > at org.elasticsearch.cluster.service.InternalClusterService$2$1. > > > run(InternalClusterService.java:237) > > > at java.util.concurrent.ThreadPoolExecutor.runWorker( > > > ThreadPoolExecutor.java:1145) > > > at java.util.concurrent.ThreadPoolExecutor$Worker.run( > > > ThreadPoolExecutor.java:615) > > > at java.lang.Thread.run(Thread.java:744) > > > > > > I saw in elasticsearch code that > > > > > > public abstract class MasterNodeOperationRequest extends ActionRequest { > > > > > > ``` > > > public static TimeValue DEFAULT_MASTER_NODE_TIMEOUT = > > > > > > ``` > > > > > > TimeValue.timeValueSeconds(30); > > > > > > ``` > > > protected TimeValue masterNodeTimeout = DEFAULT_MASTER_NODE_TIMEOUT; > > > > > > ``` > > > > > > Thanks, > > > Munna > > > > > > -- > > > 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 [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com). > > > To view this discussion on the web visit [https://groups.google.com/d/](https://groups.google.com/d/) > > > msgid/elasticsearch/8ee9ef0f-e1f2-4230-a7cf-1dfec4eee9b7% > > > [40googlegroups.com](http://40googlegroups.com). > > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). > > > > -- > > You received this message because you are subscribed to a topic in the > > Google Groups "elasticsearch" group. > > To unsubscribe from this topic, visit > > [https://groups.google.com/d/topic/elasticsearch/JksDMKjvKvA/unsubscribe](https://groups.google.com/d/topic/elasticsearch/JksDMKjvKvA/unsubscribe). > > To unsubscribe from this group and all its topics, send an email to > > [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > > To view this discussion on the web visit > > [https://groups.google.com/d/msgid/elasticsearch/9a0bd096-ce5d-4f2e-9f2d-9c5c34fd374b%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/9a0bd096-ce5d-4f2e-9f2d-9c5c34fd374b%40googlegroups.com) > > . > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- 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). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CACAuqNukAczguh7zjfwi3kTVzTekkFz%2BMSw0Vm\_9xx2K7va05Q%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CACAuqNukAczguh7zjfwi3kTVzTekkFz%2BMSw0Vm_9xx2K7va05Q%40mail.gmail.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![javanna](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/javanna/32/4698_2.png) [@javanna](https://discuss.elastic.co/u/javanna)\ **Post date:** [January 30, 2014, 9:38am UTC](https://discuss.elastic.co/t/processclustereventtimeoutexception-in-elasticsearch-is-this-timeout-value-configurable-if-yes-how/15458/5 "2014-01-30T09:38:31Z")
I see, but now I'm curious on why it takes so long for you to create aliases, 30 secs seems to be a reasonable default. On Wed, Jan 29, 2014 at 9:26 PM, Ahaduzzaman Munna \< [ahaduzzaman.munna@gmail.com](mailto:ahaduzzaman.munna@gmail.com)\> wrote: > Yes, I feel its little inconvenient not to have that default value > configurable via the config file or an API. I hope ES team do something > about it. > I didn't want to touch my code rather I wanted to have some global > configurable setting to make my life easy .... > > On Wed, Jan 29, 2014 at 12:07 PM, Luca Cavanna [cavannaluca@gmail.com](mailto:cavannaluca@gmail.com)wrote: > > > The master node timeout is configurable on each call using the > > master\_timeout parameter. There's no global default exposed as settings > > though. > > > > Cheers > > Luca > > > > On Wednesday, January 29, 2014 6:32:07 PM UTC+1, Ivan Brusic wrote: > > > > > It appears that this value is not configurable. IMHO, it should be, so > > > perhaps you should open an issue on Github and see if the elasticsearch > > > team agrees. Better yet, submit a pull request. 🙂 > > > > > > -- > > > Ivan > > > > > > On Tue, Jan 28, 2014 at 1:08 PM, Ahaduzzaman Munna \< > > > [ahaduzza...@gmail.com](mailto:ahaduzza...@gmail.com)\> wrote: > > > > > > > Getting timeout exceptions like below for different index operations. > > > > Below one shows for "index-aliases" operation. I would like to know how > > > > can I configure this timeout value in elasticsearch.yml so that I configure > > > > it once and I do not have to worry about this timeout exception. > > > > > > > > org.elasticsearch.cluster.metadata.ProcessClusterEventTimeoutException: > > > > failed to process cluster event (index-aliases) within 30s > > > > at org.elasticsearch.cluster.service.InternalClusterService$2$1. > > > > run(InternalClusterService.java:237) > > > > at java.util.concurrent.ThreadPoolExecutor.runWorker( > > > > ThreadPoolExecutor.java:1145) > > > > at java.util.concurrent.ThreadPoolExecutor$Worker.run( > > > > ThreadPoolExecutor.java:615) > > > > at java.lang.Thread.run(Thread.java:744) > > > > > > > > I saw in elasticsearch code that > > > > > > > > public abstract class MasterNodeOperationRequest extends ActionRequest { > > > > > > > > ``` > > > > public static TimeValue DEFAULT_MASTER_NODE_TIMEOUT = > > > > > > > > ``` > > > > > > > > TimeValue.timeValueSeconds(30); > > > > > > > > ``` > > > > protected TimeValue masterNodeTimeout = DEFAULT_MASTER_NODE_TIMEOUT; > > > > > > > > ``` > > > > > > > > Thanks, > > > > Munna > > > > > > > > -- > > > > 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 [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com). > > > > To view this discussion on the web visit [https://groups.google.com/d/](https://groups.google.com/d/) > > > > msgid/elasticsearch/8ee9ef0f-e1f2-4230-a7cf-1dfec4eee9b7% > > > > [40googlegroups.com](http://40googlegroups.com). > > > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). > > > > > > -- > > > You received this message because you are subscribed to a topic in the > > > Google Groups "elasticsearch" group. > > > To unsubscribe from this topic, visit > > > [https://groups.google.com/d/topic/elasticsearch/JksDMKjvKvA/unsubscribe](https://groups.google.com/d/topic/elasticsearch/JksDMKjvKvA/unsubscribe). > > > To unsubscribe from this group and all its topics, send an email to > > > [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > > > To view this discussion on the web visit > > > [https://groups.google.com/d/msgid/elasticsearch/9a0bd096-ce5d-4f2e-9f2d-9c5c34fd374b%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/9a0bd096-ce5d-4f2e-9f2d-9c5c34fd374b%40googlegroups.com) > > > . > > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). > > -- > You received this message because you are subscribed to a topic in the > Google Groups "elasticsearch" group. > To unsubscribe from this topic, visit > [https://groups.google.com/d/topic/elasticsearch/JksDMKjvKvA/unsubscribe](https://groups.google.com/d/topic/elasticsearch/JksDMKjvKvA/unsubscribe). > To unsubscribe from this group and all its topics, send an email to > [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/CACAuqNukAczguh7zjfwi3kTVzTekkFz%2BMSw0Vm\_9xx2K7va05Q%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CACAuqNukAczguh7zjfwi3kTVzTekkFz%2BMSw0Vm_9xx2K7va05Q%40mail.gmail.com) > . > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- 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). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CADdZ9MWk1M4Anqv\_c7\_BxFhas\_CLXtzqQpzzFdG8v-k%3DwQC59w%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CADdZ9MWk1M4Anqv_c7_BxFhas_CLXtzqQpzzFdG8v-k%3DwQC59w%40mail.gmail.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Munna](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/munna/32/1841_2.png) [@Munna](https://discuss.elastic.co/u/Munna)\ **Post date:** [January 30, 2014, 3:45pm UTC](https://discuss.elastic.co/t/processclustereventtimeoutexception-in-elasticsearch-is-this-timeout-value-configurable-if-yes-how/15458/6 "2014-01-30T15:45:59Z")
Well. Thats a separate issue. I do not know what exactly happens at ES side for any index operation. But if it the master timeout is configurable at once, then it solves a lot of problems. On Thu, Jan 30, 2014 at 3:38 AM, Luca Cavanna [cavannaluca@gmail.com](mailto:cavannaluca@gmail.com) wrote: > I see, but now I'm curious on why it takes so long for you to create > aliases, 30 secs seems to be a reasonable default. > > On Wed, Jan 29, 2014 at 9:26 PM, Ahaduzzaman Munna \< > [ahaduzzaman.munna@gmail.com](mailto:ahaduzzaman.munna@gmail.com)\> wrote: > > > Yes, I feel its little inconvenient not to have that default value > > configurable via the config file or an API. I hope ES team do something > > about it. > > I didn't want to touch my code rather I wanted to have some global > > configurable setting to make my life easy .... > > > > On Wed, Jan 29, 2014 at 12:07 PM, Luca Cavanna [cavannaluca@gmail.com](mailto:cavannaluca@gmail.com)wrote: > > > > > The master node timeout is configurable on each call using the > > > master\_timeout parameter. There's no global default exposed as settings > > > though. > > > > > > Cheers > > > Luca > > > > > > On Wednesday, January 29, 2014 6:32:07 PM UTC+1, Ivan Brusic wrote: > > > > > > > It appears that this value is not configurable. IMHO, it should be, so > > > > perhaps you should open an issue on Github and see if the elasticsearch > > > > team agrees. Better yet, submit a pull request. 🙂 > > > > > > > > -- > > > > Ivan > > > > > > > > On Tue, Jan 28, 2014 at 1:08 PM, Ahaduzzaman Munna \< > > > > [ahaduzza...@gmail.com](mailto:ahaduzza...@gmail.com)\> wrote: > > > > > > > > > Getting timeout exceptions like below for different index operations. > > > > > Below one shows for "index-aliases" operation. I would like to know how > > > > > can I configure this timeout value in elasticsearch.yml so that I configure > > > > > it once and I do not have to worry about this timeout exception. > > > > > > > > > > org.elasticsearch.cluster.metadata.ProcessClusterEventTimeoutException: > > > > > failed to process cluster event (index-aliases) within 30s > > > > > at org.elasticsearch.cluster.service.InternalClusterService$2$1. > > > > > run(InternalClusterService.java:237) > > > > > at java.util.concurrent.ThreadPoolExecutor.runWorker( > > > > > ThreadPoolExecutor.java:1145) > > > > > at java.util.concurrent.ThreadPoolExecutor$Worker.run( > > > > > ThreadPoolExecutor.java:615) > > > > > at java.lang.Thread.run(Thread.java:744) > > > > > > > > > > I saw in elasticsearch code that > > > > > > > > > > public abstract class MasterNodeOperationRequest extends ActionRequest { > > > > > > > > > > ``` > > > > > public static TimeValue DEFAULT_MASTER_NODE_TIMEOUT = > > > > > > > > > > ``` > > > > > > > > > > TimeValue.timeValueSeconds(30); > > > > > > > > > > ``` > > > > > protected TimeValue masterNodeTimeout = > > > > > > > > > > ``` > > > > > > > > > > DEFAULT\_MASTER\_NODE\_TIMEOUT; > > > > > > > > > > Thanks, > > > > > Munna > > > > > > > > > > -- > > > > > 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 [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com). > > > > > To view this discussion on the web visit [https://groups.google.com/d/](https://groups.google.com/d/) > > > > > msgid/elasticsearch/8ee9ef0f-e1f2-4230-a7cf-1dfec4eee9b7% > > > > > [40googlegroups.com](http://40googlegroups.com). > > > > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). > > > > > > > > -- > > > > You received this message because you are subscribed to a topic in the > > > > Google Groups "elasticsearch" group. > > > > To unsubscribe from this topic, visit > > > > [https://groups.google.com/d/topic/elasticsearch/JksDMKjvKvA/unsubscribe](https://groups.google.com/d/topic/elasticsearch/JksDMKjvKvA/unsubscribe). > > > > To unsubscribe from this group and all its topics, send an email to > > > > [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > > > > To view this discussion on the web visit > > > > [https://groups.google.com/d/msgid/elasticsearch/9a0bd096-ce5d-4f2e-9f2d-9c5c34fd374b%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/9a0bd096-ce5d-4f2e-9f2d-9c5c34fd374b%40googlegroups.com) > > > > . > > > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). > > > > -- > > You received this message because you are subscribed to a topic in the > > Google Groups "elasticsearch" group. > > To unsubscribe from this topic, visit > > [https://groups.google.com/d/topic/elasticsearch/JksDMKjvKvA/unsubscribe](https://groups.google.com/d/topic/elasticsearch/JksDMKjvKvA/unsubscribe). > > To unsubscribe from this group and all its topics, send an email to > > [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > > To view this discussion on the web visit > > [https://groups.google.com/d/msgid/elasticsearch/CACAuqNukAczguh7zjfwi3kTVzTekkFz%2BMSw0Vm\_9xx2K7va05Q%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CACAuqNukAczguh7zjfwi3kTVzTekkFz%2BMSw0Vm_9xx2K7va05Q%40mail.gmail.com) > > . > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). > > -- > You received this message because you are subscribed to a topic in the > Google Groups "elasticsearch" group. > To unsubscribe from this topic, visit > [https://groups.google.com/d/topic/elasticsearch/JksDMKjvKvA/unsubscribe](https://groups.google.com/d/topic/elasticsearch/JksDMKjvKvA/unsubscribe). > To unsubscribe from this group and all its topics, send an email to > [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/CADdZ9MWk1M4Anqv\_c7\_BxFhas\_CLXtzqQpzzFdG8v-k%3DwQC59w%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CADdZ9MWk1M4Anqv_c7_BxFhas_CLXtzqQpzzFdG8v-k%3DwQC59w%40mail.gmail.com) > . > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- 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). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CACAuqNuDL2Dhy%2BO8b1nAvRjnXULokmDuFzYc2oasWrb40JpSMA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CACAuqNuDL2Dhy%2BO8b1nAvRjnXULokmDuFzYc2oasWrb40JpSMA%40mail.gmail.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![am87](https://avatars.discourse-cdn.com/v4/letter/a/e36b37/32.png) [@am87](https://discuss.elastic.co/u/am87)\ **Post date:** [May 25, 2015, 6:36pm UTC](https://discuss.elastic.co/t/processclustereventtimeoutexception-in-elasticsearch-is-this-timeout-value-configurable-if-yes-how/15458/7 "2015-05-25T18:36:50Z")
Could someone please give an example of how to go about configuring this value, or how/where to provide master\_timeout? I'm getting a similar issue when creating mappings, not sure how to go about fixing it. I've read something in the docs about a zen.discovery.publish\_timeout, but I believe that's something different [2015-05-22 12:40:06,000][DEBUG][action.admin.indices.mapping.put] failed to put mappings on indices [index\_1432298356915]], type [stuff] org.elasticsearch.cluster.metadata.ProcessClusterEventTimeoutException: failed to process cluster event (put-mapping [stuff]) within 30s at org.elasticsearch.cluster.service.InternalClusterService$2$1.run(InternalClusterService.java:270) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) On Thursday, 30 January 2014 15:45:59 UTC, Ahaduzzaman Munna wrote: > Well. Thats a separate issue. I do not know what exactly happens at ES > side for any index operation. But if it the master timeout is configurable > at once, then it solves a lot of problems. > > On Thu, Jan 30, 2014 at 3:38 AM, Luca Cavanna \<[cavan...@gmail.com](mailto:cavan...@gmail.com) > \\> wrote: > > > I see, but now I'm curious on why it takes so long for you to create > > aliases, 30 secs seems to be a reasonable default. > > > > On Wed, Jan 29, 2014 at 9:26 PM, Ahaduzzaman Munna \<[ahaduzza...@gmail.com](mailto:ahaduzza...@gmail.com) > > \\> wrote: > > > > > Yes, I feel its little inconvenient not to have that default value > > > configurable via the config file or an API. I hope ES team do something > > > about it. > > > I didn't want to touch my code rather I wanted to have some global > > > configurable setting to make my life easy .... > > > > > > On Wed, Jan 29, 2014 at 12:07 PM, Luca Cavanna \<[cavan...@gmail.com](mailto:cavan...@gmail.com) > > > \\> wrote: > > > > > > > The master node timeout is configurable on each call using the > > > > master\_timeout parameter. There's no global default exposed as settings > > > > though. > > > > > > > > Cheers > > > > Luca > > > > > > > > On Wednesday, January 29, 2014 6:32:07 PM UTC+1, Ivan Brusic wrote: > > > > > > > > > It appears that this value is not configurable. IMHO, it should be, so > > > > > perhaps you should open an issue on Github and see if the elasticsearch > > > > > team agrees. Better yet, submit a pull request. 🙂 > > > > > > > > > > -- > > > > > Ivan > > > > > > > > > > On Tue, Jan 28, 2014 at 1:08 PM, Ahaduzzaman Munna \< > > > > > [ahaduzza...@gmail.com](mailto:ahaduzza...@gmail.com)\> wrote: > > > > > > > > > > > Getting timeout exceptions like below for different index operations. > > > > > > Below one shows for "index-aliases" operation. I would like to know how > > > > > > can I configure this timeout value in elasticsearch.yml so that I configure > > > > > > it once and I do not have to worry about this timeout exception. > > > > > > > > > > > > org.elasticsearch.cluster.metadata.ProcessClusterEventTimeoutException: > > > > > > failed to process cluster event (index-aliases) within 30s > > > > > > at org.elasticsearch.cluster.service.InternalClusterService$2$1. > > > > > > run(InternalClusterService.java:237) > > > > > > at java.util.concurrent.ThreadPoolExecutor.runWorker( > > > > > > ThreadPoolExecutor.java:1145) > > > > > > at java.util.concurrent.ThreadPoolExecutor$Worker.run( > > > > > > ThreadPoolExecutor.java:615) > > > > > > at java.lang.Thread.run(Thread.java:744) > > > > > > > > > > > > I saw in elasticsearch code that > > > > > > > > > > > > public abstract class MasterNodeOperationRequest extends ActionRequest { > > > > > > > > > > > > ``` > > > > > > public static TimeValue DEFAULT_MASTER_NODE_TIMEOUT = > > > > > > > > > > > > ``` > > > > > > > > > > > > TimeValue.timeValueSeconds(30); > > > > > > > > > > > > ``` > > > > > > protected TimeValue masterNodeTimeout = > > > > > > > > > > > > ``` > > > > > > > > > > > > DEFAULT\_MASTER\_NODE\_TIMEOUT; > > > > > > > > > > > > Thanks, > > > > > > Munna > > > > > > > > > > > > -- > > > > > > 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 [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com). > > > > > > To view this discussion on the web visit [https://groups.google.com/d/](https://groups.google.com/d/) > > > > > > msgid/elasticsearch/8ee9ef0f-e1f2-4230-a7cf-1dfec4eee9b7% > > > > > > [40googlegroups.com](http://40googlegroups.com). > > > > > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). > > > > > > > > > > -- > > > > > You received this message because you are subscribed to a topic in the > > > > > Google Groups "elasticsearch" group. > > > > > To unsubscribe from this topic, visit > > > > > [https://groups.google.com/d/topic/elasticsearch/JksDMKjvKvA/unsubscribe](https://groups.google.com/d/topic/elasticsearch/JksDMKjvKvA/unsubscribe) > > > > > . > > > > > To unsubscribe from this group and all its topics, send an email to > > > > > [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \. > > > > > To view this discussion on the web visit > > > > > [https://groups.google.com/d/msgid/elasticsearch/9a0bd096-ce5d-4f2e-9f2d-9c5c34fd374b%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/9a0bd096-ce5d-4f2e-9f2d-9c5c34fd374b%40googlegroups.com) > > > > > . > > > > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). > > > > > > -- > > > You received this message because you are subscribed to a topic in the > > > Google Groups "elasticsearch" group. > > > To unsubscribe from this topic, visit > > > [https://groups.google.com/d/topic/elasticsearch/JksDMKjvKvA/unsubscribe](https://groups.google.com/d/topic/elasticsearch/JksDMKjvKvA/unsubscribe). > > > To unsubscribe from this group and all its topics, send an email to > > > [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \. > > > To view this discussion on the web visit > > > [https://groups.google.com/d/msgid/elasticsearch/CACAuqNukAczguh7zjfwi3kTVzTekkFz%2BMSw0Vm\_9xx2K7va05Q%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CACAuqNukAczguh7zjfwi3kTVzTekkFz%2BMSw0Vm_9xx2K7va05Q%40mail.gmail.com) > > > . > > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). > > > > -- > > You received this message because you are subscribed to a topic in the > > Google Groups "elasticsearch" group. > > To unsubscribe from this topic, visit > > [https://groups.google.com/d/topic/elasticsearch/JksDMKjvKvA/unsubscribe](https://groups.google.com/d/topic/elasticsearch/JksDMKjvKvA/unsubscribe). > > To unsubscribe from this group and all its topics, send an email to > > [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \. > > To view this discussion on the web visit > > [https://groups.google.com/d/msgid/elasticsearch/CADdZ9MWk1M4Anqv\_c7\_BxFhas\_CLXtzqQpzzFdG8v-k%3DwQC59w%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CADdZ9MWk1M4Anqv_c7_BxFhas_CLXtzqQpzzFdG8v-k%3DwQC59w%40mail.gmail.com) > > . > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ## -- Please update your bookmarks! We have moved to [https://discuss.elastic.co/](https://discuss.elastic.co/) 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). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/5171dd69-381f-48ca-8a0d-709c0588a9f3%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/5171dd69-381f-48ca-8a0d-709c0588a9f3%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [May 26, 2015, 12:52am UTC](https://discuss.elastic.co/t/processclustereventtimeoutexception-in-elasticsearch-is-this-timeout-value-configurable-if-yes-how/15458/8 "2015-05-26T00:52:02Z")
This thread is nearly 18 months old, you should really create a new one with a little more detail. PS - We're moving to [https://discuss.elastic.co/](https://discuss.elastic.co/), please join us there for any future discussions! On 26 May 2015 at 04:36, mzrth\_7810 [afrazmamoon@gmail.com](mailto:afrazmamoon@gmail.com) wrote: > Could someone please give an example of how to go about configuring this > value, or how/where to provide master\_timeout? I'm getting a similar issue > when creating mappings, not sure how to go about fixing it. I've read > something in the docs about a zen.discovery.publish\_timeout, but I believe > that's something different > > [2015-05-22 12:40:06,000][DEBUG][action.admin.indices.mapping.put] failed > to put mappings on indices [index\_1432298356915]], type [stuff] > org.elasticsearch.cluster.metadata.ProcessClusterEventTimeoutException: > failed to process cluster event (put-mapping [stuff]) within 30s at > org.elasticsearch.cluster.service.InternalClusterService$2$1.run(InternalClusterService.java:270) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > > On Thursday, 30 January 2014 15:45:59 UTC, Ahaduzzaman Munna wrote: > > > Well. Thats a separate issue. I do not know what exactly happens at ES > > side for any index operation. But if it the master timeout is configurable > > at once, then it solves a lot of problems. > > > > On Thu, Jan 30, 2014 at 3:38 AM, Luca Cavanna [cavan...@gmail.com](mailto:cavan...@gmail.com) wrote: > > > > > I see, but now I'm curious on why it takes so long for you to create > > > aliases, 30 secs seems to be a reasonable default. > > > > > > On Wed, Jan 29, 2014 at 9:26 PM, Ahaduzzaman Munna \< > > > [ahaduzza...@gmail.com](mailto:ahaduzza...@gmail.com)\> wrote: > > > > > > > Yes, I feel its little inconvenient not to have that default value > > > > configurable via the config file or an API. I hope ES team do something > > > > about it. > > > > I didn't want to touch my code rather I wanted to have some global > > > > configurable setting to make my life easy .... > > > > > > > > On Wed, Jan 29, 2014 at 12:07 PM, Luca Cavanna [cavan...@gmail.com](mailto:cavan...@gmail.com) > > > > wrote: > > > > > > > > > The master node timeout is configurable on each call using the > > > > > master\_timeout parameter. There's no global default exposed as settings > > > > > though. > > > > > > > > > > Cheers > > > > > Luca > > > > > > > > > > On Wednesday, January 29, 2014 6:32:07 PM UTC+1, Ivan Brusic wrote: > > > > > > > > > > > It appears that this value is not configurable. IMHO, it should be, > > > > > > so perhaps you should open an issue on Github and see if the elasticsearch > > > > > > team agrees. Better yet, submit a pull request. 🙂 > > > > > > > > > > > > -- > > > > > > Ivan > > > > > > > > > > > > On Tue, Jan 28, 2014 at 1:08 PM, Ahaduzzaman Munna \< > > > > > > [ahaduzza...@gmail.com](mailto:ahaduzza...@gmail.com)\> wrote: > > > > > > > > > > > > > Getting timeout exceptions like below for different index > > > > > > > operations. Below one shows for "index-aliases" operation. I would like to > > > > > > > know how can I configure this timeout value in elasticsearch.yml so that I > > > > > > > configure it once and I do not have to worry about this timeout exception. > > > > > > > > > > > > > > org.elasticsearch.cluster.metadata.ProcessClusterEventTimeoutException: > > > > > > > failed to process cluster event (index-aliases) within 30s > > > > > > > at org.elasticsearch.cluster.service.InternalClusterService$2$1. > > > > > > > run(InternalClusterService.java:237) > > > > > > > at java.util.concurrent.ThreadPoolExecutor.runWorker( > > > > > > > ThreadPoolExecutor.java:1145) > > > > > > > at java.util.concurrent.ThreadPoolExecutor$Worker.run( > > > > > > > ThreadPoolExecutor.java:615) > > > > > > > at java.lang.Thread.run(Thread.java:744) > > > > > > > > > > > > > > I saw in elasticsearch code that > > > > > > > > > > > > > > public abstract class MasterNodeOperationRequest extends ActionRequest { > > > > > > > > > > > > > > ``` > > > > > > > public static TimeValue DEFAULT_MASTER_NODE_TIMEOUT = > > > > > > > > > > > > > > ``` > > > > > > > > > > > > > > TimeValue.timeValueSeconds(30); > > > > > > > > > > > > > > ``` > > > > > > > protected TimeValue masterNodeTimeout = > > > > > > > > > > > > > > ``` > > > > > > > > > > > > > > DEFAULT\_MASTER\_NODE\_TIMEOUT; > > > > > > > > > > > > > > Thanks, > > > > > > > Munna > > > > > > > > > > > > > > -- > > > > > > > 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 [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com). > > > > > > > To view this discussion on the web visit > > > > > > > [https://groups.google.com/d/msgid/elasticsearch/8ee9ef0f-](https://groups.google.com/d/msgid/elasticsearch/8ee9ef0f-) > > > > > > > e1f2-4230-a7cf-1dfec4eee9b7%[40googlegroups.com](http://40googlegroups.com). > > > > > > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). > > > > > > > > > > > > -- > > > > > > You received this message because you are subscribed to a topic in the > > > > > > Google Groups "elasticsearch" group. > > > > > > To unsubscribe from this topic, visit > > > > > > [https://groups.google.com/d/topic/elasticsearch/JksDMKjvKvA/unsubscribe](https://groups.google.com/d/topic/elasticsearch/JksDMKjvKvA/unsubscribe) > > > > > > . > > > > > > To unsubscribe from this group and all its topics, send an email to > > > > > > [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com). > > > > > > To view this discussion on the web visit > > > > > > [https://groups.google.com/d/msgid/elasticsearch/9a0bd096-ce5d-4f2e-9f2d-9c5c34fd374b%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/9a0bd096-ce5d-4f2e-9f2d-9c5c34fd374b%40googlegroups.com) > > > > > > . > > > > > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). > > > > > > > > -- > > > > You received this message because you are subscribed to a topic in the > > > > Google Groups "elasticsearch" group. > > > > To unsubscribe from this topic, visit > > > > [https://groups.google.com/d/topic/elasticsearch/JksDMKjvKvA/unsubscribe](https://groups.google.com/d/topic/elasticsearch/JksDMKjvKvA/unsubscribe) > > > > . > > > > To unsubscribe from this group and all its topics, send an email to > > > > [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com). > > > > To view this discussion on the web visit > > > > [https://groups.google.com/d/msgid/elasticsearch/CACAuqNukAczguh7zjfwi3kTVzTekkFz%2BMSw0Vm\_9xx2K7va05Q%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CACAuqNukAczguh7zjfwi3kTVzTekkFz%2BMSw0Vm_9xx2K7va05Q%40mail.gmail.com) > > > > . > > > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). > > > > > > -- > > > You received this message because you are subscribed to a topic in the > > > Google Groups "elasticsearch" group. > > > To unsubscribe from this topic, visit > > > [https://groups.google.com/d/topic/elasticsearch/JksDMKjvKvA/unsubscribe](https://groups.google.com/d/topic/elasticsearch/JksDMKjvKvA/unsubscribe). > > > To unsubscribe from this group and all its topics, send an email to > > > [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com). > > > To view this discussion on the web visit > > > [https://groups.google.com/d/msgid/elasticsearch/CADdZ9MWk1M4Anqv\_c7\_BxFhas\_CLXtzqQpzzFdG8v-k%3DwQC59w%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CADdZ9MWk1M4Anqv_c7_BxFhas_CLXtzqQpzzFdG8v-k%3DwQC59w%40mail.gmail.com) > > > . > > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). > > > > -- > > Please update your bookmarks! We have moved to [https://discuss.elastic.co/](https://discuss.elastic.co/) > > * * * > > 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). > To view this discussion on the web visit > [https://groups.google.com/d/msgid/elasticsearch/5171dd69-381f-48ca-8a0d-709c0588a9f3%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/5171dd69-381f-48ca-8a0d-709c0588a9f3%40googlegroups.com) > [https://groups.google.com/d/msgid/elasticsearch/5171dd69-381f-48ca-8a0d-709c0588a9f3%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/5171dd69-381f-48ca-8a0d-709c0588a9f3%40googlegroups.com?utm_medium=email&utm_source=footer) > . > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ## -- Please update your bookmarks! We have moved to [https://discuss.elastic.co/](https://discuss.elastic.co/) 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). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAEYi1X-x%3DNjJKUq1oWB5ocJuRiqhkoLzD9kGMFXbJkTS5e6FmA%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAEYi1X-x%3DNjJKUq1oWB5ocJuRiqhkoLzD9kGMFXbJkTS5e6FmA%40mail.gmail.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![nmanandhan](https://avatars.discourse-cdn.com/v4/letter/n/cdc98d/32.png) [@nmanandhan](https://discuss.elastic.co/u/nmanandhan)\ **Post date:** [September 2, 2015, 11:41am UTC](https://discuss.elastic.co/t/processclustereventtimeoutexception-in-elasticsearch-is-this-timeout-value-configurable-if-yes-how/15458/9 "2015-09-02T11:41:06Z")
we are getting this exception very often while running operational scripts to create index/add alias.IMHO it would be better to have global configuration for master\_timeout property. Do we have any update on this thread? ---
**Author:** ![nivethav](https://avatars.discourse-cdn.com/v4/letter/n/4bbf92/32.png) [@nivethav](https://discuss.elastic.co/u/nivethav)\ **Post date:** [February 19, 2016, 12:09am UTC](https://discuss.elastic.co/t/processclustereventtimeoutexception-in-elasticsearch-is-this-timeout-value-configurable-if-yes-how/15458/10 "2016-02-19T00:09:44Z")
We are getting these timeout exceptions very frequently when creating an index or updating a mapping on an index. I would like to understand why these timeouts happen? Why does it require more than 30 seconds to create an index or update mapping? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 5, 2017, 11:15pm UTC](https://discuss.elastic.co/t/processclustereventtimeoutexception-in-elasticsearch-is-this-timeout-value-configurable-if-yes-how/15458/11 "2017-07-05T23:15:04Z")