# Curator shows Job completed but no action

**URL:** https://discuss.elastic.co/t/curator-shows-job-completed-but-no-action/77821
**Category:** Elasticsearch
**Created:** [March 8, 2017, 1:25pm UTC](https://discuss.elastic.co/t/curator-shows-job-completed-but-no-action/77821 "2017-03-08T13:25:06Z")
**Posts on this page:** 11
**Page:** 1

<div class="post-metadata">

### Author: ![newbie\_here](https://avatars.discourse-cdn.com/v4/letter/n/dbc845/32.png) [@newbie\_here](https://discuss.elastic.co/u/newbie_here)
#### Post date: [March 8, 2017, 1:25pm UTC](https://discuss.elastic.co/t/curator-shows-job-completed-but-no-action/77821/1 "2017-03-08T13:25:06Z")

</div>

Hi,  
I am testing curator to create a new index in Elasticsearch 5.1.1. Following are my config and action file respectively

Config File :-  
client:  
hosts:  
- localhost  
port:  
- 9200  
url\_prefix:  
use\_ssl: False  
certificate:  
client\_cert:  
client\_key:  
aws\_key:  
aws\_secret\_key:  
aws\_region:  
ssl\_no\_validate: False  
timeout: 30  
master\_only: False

Action File :-  
actions:  
1:  
action: create\_index  
description: "Create index as named"  
options:  
name: new\_index  
extra\_settings:  
settings:  
number\_of\_shards: 1  
number\_of\_replicas: 0  
timeout\_override:  
continue\_if\_exception: false  
disable\_action: false

After running it by the command  
curator --config C:\Users\user\Desktop\config.yml --dry-run C:\Users\user\Desktop\file.yml

It shows the message

2017-03-08 18:02:58,316 INFO Preparing Action ID: 1, "create\_index"  
2017-03-08 18:02:58,363 INFO Trying Action ID: 1, "create\_index": Create index as named  
2017-03-08 18:02:58,363 INFO DRY-RUN MODE. No changes will be made.  
2017-03-08 18:02:58,363 INFO DRY-RUN: create\_index "new\_index" with arguments: {'settings': {'number\_of\_shards': 1, 'number\_of\_replicas': 0}}  
2017-03-08 18:02:58,363 INFO Action ID: 1, "create\_index" completed.  
2017-03-08 18:02:58,379 INFO Job completed.

But after running curl localhost:9200/\_cat/indices , I don't see any new index created.

I feel like there is a problem in the config file most probably. Please help me out.

P.S :- I have also used 127.0.0.1 and local machine IP in the host

---

<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: [March 8, 2017, 4:50pm UTC](https://discuss.elastic.co/t/curator-shows-job-completed-but-no-action/77821/2 "2017-03-08T16:50:20Z")

</div>

If you continue to run with the `--dry-run` flag, no changes will ever be made. That flag is used to test what the actions should do _without_ actually doing them.

---

<div class="post-metadata">

### Author: ![newbie\_here](https://avatars.discourse-cdn.com/v4/letter/n/dbc845/32.png) [@newbie\_here](https://discuss.elastic.co/u/newbie_here)
#### Post date: [March 9, 2017, 6:15am UTC](https://discuss.elastic.co/t/curator-shows-job-completed-but-no-action/77821/3 "2017-03-09T06:15:01Z")

</div>

Thank You . It did work. Looking at the guide in the curator I thought --dry-run parameter works with making no deviation from your action file.

Continuing working with curator, I am facing one more problem. Below is my action file  
actions:  
1:  
action: delete\_indices  
description: "Delete Selected Indices"  
options:  
timeout\_override:  
continue\_if\_exception: false  
disable\_action: false  
filters:  
- filtertype: age  
source: name  
direction: younger  
timestring: '%Y.%m.%d'  
unit: days  
unit\_count: 2

When I run this, I get the following message :-  
No actionable items in list: \<class 'curator.exceptions.NoIndices'\>

I think the curator is not getting my filter, is there some problem with the syntax?

---

<div class="post-metadata">

### Author: ![newbie\_here](https://avatars.discourse-cdn.com/v4/letter/n/dbc845/32.png) [@newbie\_here](https://discuss.elastic.co/u/newbie_here)
#### Post date: [March 9, 2017, 6:29am UTC](https://discuss.elastic.co/t/curator-shows-job-completed-but-no-action/77821/4 "2017-03-09T06:29:13Z")

</div>

Also I saw this issue of shard\_reallocation problem :-

> <https://github.com/elastic/curator/issues/871>

Do, I have to wait for Curator 5.x for the shard allocation action to work in Elasticsearch 5.1.1

Thanks in advance

---

<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: [March 9, 2017, 6:41am UTC](https://discuss.elastic.co/t/curator-shows-job-completed-but-no-action/77821/5 "2017-03-09T06:41:02Z")

</div>

2 days younger than now is in the future, so I'm not surprised there are no actionable indices. You probably meant to use `older`

---

<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: [March 9, 2017, 6:44am UTC](https://discuss.elastic.co/t/curator-shows-job-completed-but-no-action/77821/6 "2017-03-09T06:44:19Z")

</div>

Allocation still works, you just can't use the `wait_for_completion` flag until the patched version is released.

---

<div class="post-metadata">

### Author: ![newbie\_here](https://avatars.discourse-cdn.com/v4/letter/n/dbc845/32.png) [@newbie\_here](https://discuss.elastic.co/u/newbie_here)
#### Post date: [March 9, 2017, 7:09am UTC](https://discuss.elastic.co/t/curator-shows-job-completed-but-no-action/77821/7 "2017-03-09T07:09:14Z")

</div>

So I have had this confusion. If I use older and set unit\_count : 2 ;  
It means indices older than 2 days or indices age = (0,2)

Thanks in advance

---

<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: [March 9, 2017, 6:30pm UTC](https://discuss.elastic.co/t/curator-shows-job-completed-but-no-action/77821/8 "2017-03-09T18:30:08Z")

</div>

Indices older than 2 days from program start time, as identified by the settings in the filter.

---

<div class="post-metadata">

### Author: ![newbie\_here](https://avatars.discourse-cdn.com/v4/letter/n/dbc845/32.png) [@newbie\_here](https://discuss.elastic.co/u/newbie_here)
#### Post date: [March 10, 2017, 1:46pm UTC](https://discuss.elastic.co/t/curator-shows-job-completed-but-no-action/77821/9 "2017-03-10T13:46:36Z")

</div>

Thank You for you help.

I have a final query, a help required for our production environment.

If I use document routing and allocate one doctype to be in 1 or 2 shards and other doctypes in other shards. Is it possible for us to route the doctype into the warm nodes while the other shards of the index stays in the hot nodes.

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: [March 10, 2017, 2:10pm UTC](https://discuss.elastic.co/t/curator-shows-job-completed-but-no-action/77821/10 "2017-03-10T14:10:23Z")

</div>

Since that is only tangentially related to this topic, please ask in a new topic.

---

<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: [April 7, 2017, 2:10pm UTC](https://discuss.elastic.co/t/curator-shows-job-completed-but-no-action/77821/11 "2017-04-07T14:10:26Z")

</div>

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