# Curator snapshot action timeout override

**URL:** <https://discuss.elastic.co/t/curator-snapshot-action-timeout-override/58362>\
**Category:** Elasticsearch\
**Created:** [August 18, 2016, 2:47pm UTC](https://discuss.elastic.co/t/curator-snapshot-action-timeout-override/58362 "2016-08-18T14:47:41Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![KrzysztofSendor](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/krzysztofsendor/32/11456_2.png) [@KrzysztofSendor](https://discuss.elastic.co/u/KrzysztofSendor)\
**Post date:** [August 18, 2016, 2:47pm UTC](https://discuss.elastic.co/t/curator-snapshot-action-timeout-override/58362/1 "2016-08-18T14:47:41Z")

</div>

Hi all,

I've been configuring curator and creating actions for it today and here is my question/problem.

Based on documentation found [here](https://www.elastic.co/guide/en/elasticsearch/client/curator/current/configfile.html#timeout) **default value for timeout is 30** (seconds) and in case of actions like snapshot or forcemerge **if it's set to 30 it will be automatically overridden to 21600** (at least this is how I understand it).

I'm creating snapshot to s3 and this are my configurations:

_curator.yml_

```auto
client:
    hosts:
      - 127.0.0.1
    port: 9200
    url_prefix:
    use_ssl: False
    certificate:
    client_cert:
    client_key:
    aws_key:
    aws_secret_key:
    aws_region:
    ssl_no_validate: False
    http_auth:
    timeout: 30
    master_only: False

logging:
    loglevel: INFO
    logfile:
    logformat: default
    blacklist: ['elasticsearch', 'urllib3']

```

_action.yml_

```auto
 actions:
    1:
        action: snapshot
        description: Creating snapshot of machinelog older than 14 days.
        options:
            repository: test_s3_backup
            name: somename-%Y%m%d%H%M%S
            ignore_unavailable: False
            include_global_state: True
            partial: False
            wait_for_completion: True
            skip_repo_fs_check: False
            timeout_override: 
            continue_if_exception: False
            disable_action: False
        filters:
            - filtertype: pattern
              kind: prefix
              value: somename-
              exclude: False
            - filtertype: age
              source: name
              direction: younger
              timestring: '%Y.%m.%d'
              unit: days
              unit_count: 5
              field:
              stats_result:
              epoch:
              exclude: False

```

After running it with `curator --config curator.yml action.yml` I get:

```auto
2016-08-18 14:37:08,022 ERROR Failed to complete action: snapshot. <class 'curator.exceptions.FailedExecution'>: Exception encountered. Rerun with loglevel DEBUG and/or check Elasticsearch logs for more information. Exception: ConnectionTimeout caused by - ReadTimeoutError(HTTPConnectionPool(host=u'127.0.0.1', port=9200): Read timed out. (read timeout=30))

```

I tried commenting out both `timeout` and `timeout_override`. The only way I managed to make it work is by adding enough time to `timeout_override`.

My question is:  
**Is automatic override functionality not working properly or is my configuration not correct?**  
I can set it manually in each action to 21600 but now I'm just curiuous. 😉

Thanks in advance,  
Chris

---

<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:** [August 18, 2016, 3:05pm UTC](https://discuss.elastic.co/t/curator-snapshot-action-timeout-override/58362/2 "2016-08-18T15:05:04Z")

</div>

You need to manually change the `timeout_override` for these actions for now. I initially _had_ the feature in place, but removed it when I added `timeout_override`.

But don't despair, the automatic, longer `timeout_override` for these actions will be fixed in 4.1.0 as a part of the schema validation feature being worked on right now.

Feel free to put an official issue at [https://github.com/elastic/curator](https://github.com/elastic/curator) in the meanwhile.

---

<div class="post-metadata">

**Author:** ![KrzysztofSendor](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/krzysztofsendor/32/11456_2.png) [@KrzysztofSendor](https://discuss.elastic.co/u/KrzysztofSendor)\
**Post date:** [August 19, 2016, 7:49am UTC](https://discuss.elastic.co/t/curator-snapshot-action-timeout-override/58362/3 "2016-08-19T07:49:37Z")

</div>

Thank you for your reply @theuntergeek. That clears thing up. I'll put issue at GitHub to modify documentation for time being till next release.

* * *

_edit:_  
GitHub issue can be found [here](https://github.com/elastic/curator/issues/737).

---

<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 5, 2017, 10:26pm UTC](https://discuss.elastic.co/t/curator-snapshot-action-timeout-override/58362/4 "2017-07-05T22:26:39Z")

</div>