# Curator Timout clarifications?

**URL:** <https://discuss.elastic.co/t/curator-timout-clarifications/89570>\
**Category:** Elasticsearch\
**Created:** [June 15, 2017, 2:05pm UTC](https://discuss.elastic.co/t/curator-timout-clarifications/89570 "2017-06-15T14:05:42Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Narmatha](https://avatars.discourse-cdn.com/v4/letter/n/d26b3c/32.png) [@Narmatha](https://discuss.elastic.co/u/Narmatha)\
**Post date:** [June 15, 2017, 2:05pm UTC](https://discuss.elastic.co/t/curator-timout-clarifications/89570/1 "2017-06-15T14:05:43Z")

</div>

Hi,

I have ES cluster running and i am using curator 4.2.6 to run the snapshots for indices in My ES cluster.  
My questions are:

1. IF a curator a job is running and i kept flags like `wait_for_completion : True` and `timeout: 30` Suppose my curator job takes more than 30seconds whether the job will fail?

2. Is it a good practice to increase the `timout:60` in curator configuration file or `timout_override` in action file.

Thanks

---

<div class="post-metadata">

**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:** [June 15, 2017, 10:40pm UTC](https://discuss.elastic.co/t/curator-timout-clarifications/89570/2 "2017-06-15T22:40:31Z")

</div>

> [@Narmatha](#):
>
> 1. IF a curator a job is running and i kept flags like wait\_for\_completion : True and timeout: 30 Suppose my curator job takes more than 30seconds whether the job will fail?

That depends. Several actions will [automatically override the `timeout_override`](https://github.com/elastic/curator/blob/v5.1.1/curator/defaults/option_defaults.py#L229-L239) if you have not provided a value for it. Otherwise, yes. If the client timeout is reached, Curator will log that as an error and exit, depending on the value of `continue_if_exception`. Typically, the aborted actions will continue in the background (snapshots, forceMerges, restores), or at least try to complete successfully.

> [@Narmatha](#):
>
> 1. Is it a good practice to increase the timout:60 in curator configuration file or timout\_override in action file.

Generally speaking, the default 30 second timeout is acceptable, since individual action timeouts can be set with `timeout_override`. If you have an exceptionally overtaxed or slow cluster, then a higher timeout may be desirable. If so, increasing the `timeout` setting is recommended.

---

<div class="post-metadata">

**Author:** ![Narmatha](https://avatars.discourse-cdn.com/v4/letter/n/d26b3c/32.png) [@Narmatha](https://discuss.elastic.co/u/Narmatha)\
**Post date:** [June 16, 2017, 7:09am UTC](https://discuss.elastic.co/t/curator-timout-clarifications/89570/3 "2017-06-16T07:09:20Z")

</div>

Thanks @theuntergeek[quote="theuntergeek, post:2, topic:89570"]

Several actions will automatically override the timeout\_override if you have not provided a value for it  
[/quote]

In my client configuration file i kept `timout:30` and in my snapshot action file i didn't provided value for `timout_override` and kept `continue_if_exception:false` .

Now the curator snapshot job file will run for 30s as given in client configuration file, if it didn't completed in that time then it will use the `timeout_override` that is 21600s right. That means totally 21630s the job will try for completion because i kept `wait_for_completion : True`.

If my understanding above is correct , For starting the second curator job it will be safe to start after 21630s after the first curator job.

Please correct me if i am wrong?

Thanks

---

<div class="post-metadata">

**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:** [June 16, 2017, 7:39am UTC](https://discuss.elastic.co/t/curator-timout-clarifications/89570/4 "2017-06-16T07:39:40Z")

</div>

> [@Narmatha](#):
>
> That means totally 21630s the job will try for completion because i kept wait\_for\_completion : True.

Only 21600s. It doesn't add `timeout` to `timeout_override`. One replaces the other.

Otherwise, yes, your assessment is sound.

---

<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 14, 2017, 7:39am UTC](https://discuss.elastic.co/t/curator-timout-clarifications/89570/5 "2017-07-14T07:39:41Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.