Deepak, 

Can you try the command with a hyphen at the end -   
/usr/lib/python2.6/site-packages/curator/curator.py  -d 3 -p .marvel-
For some reason, curator doesn't match the marvel indices when using 
".marvel" as the prefix.




Regards,


On Thursday, May 15, 2014 1:14:14 AM UTC+8, Deepak Subhramanian wrote:
>
> Hi Ivan/Boaz,
>
> I am getting some warning when I tried to delete the marvel index using 
> curator. 
>
> github]#  /usr/lib/python2.6/site-packages/curator/curator.py  -d 3 -p 
> .marvel
> 2014-05-14T18:07:44.691 INFO                        main:333  Job 
> starting...
> 2014-05-14T18:07:44.692 INFO                   _new_conn:180  Starting new 
> HTTP connection (1): localhost
> 2014-05-14T18:07:44.694 INFO         log_request_success:49   GET 
> http://localhost:9200/ [status:200 request:0.003s]
> 2014-05-14T18:07:44.695 INFO                        main:359  Deleting 
> indices older than 3 days...
> 2014-05-14T18:07:44.698 INFO         log_request_success:49   GET 
> http://localhost:9200/.marvel*/_settings?expand_wildcards=closed[status:200 
> request:0.002s]
> 2014-05-14T18:07:44.722 ERROR       find_expired_indices:201  Could not 
> find a valid timestamp from the index: .marvel-2014.05.07
> 2014-05-14T18:07:44.722 ERROR       find_expired_indices:201  Could not 
> find a valid timestamp from the index: .marvel-2014.05.08
> 2014-05-14T18:07:44.722 ERROR       find_expired_indices:201  Could not 
> find a valid timestamp from the index: .marvel-2014.05.09
> 2014-05-14T18:07:44.722 ERROR       find_expired_indices:201  Could not 
> find a valid timestamp from the index: .marvel-2014.05.10
> 2014-05-14T18:07:44.722 ERROR       find_expired_indices:201  Could not 
> find a valid timestamp from the index: .marvel-2014.05.11
> 2014-05-14T18:07:44.723 ERROR       find_expired_indices:201  Could not 
> find a valid timestamp from the index: .marvel-2014.05.12
> 2014-05-14T18:07:44.723 ERROR       find_expired_indices:201  Could not 
> find a valid timestamp from the index: .marvel-2014.05.13
> 2014-05-14T18:07:44.723 ERROR       find_expired_indices:201  Could not 
> find a valid timestamp from the index: .marvel-2014.05.14
> 2014-05-14T18:07:44.723 INFO                  index_loop:309  DELETE index 
> operations completed.
> 2014-05-14T18:07:44.723 INFO                        main:379  Done in 
> 0:00:00.037963.
> [root@node05 github]# ls -ltr 
> /var/lib/elasticsearch/bigdatadev/nodes/0/indices/.marvel*
> /var/lib/elasticsearch/bigdatadev/nodes/0/indices/.marvel-2014.05.10:
> total 8
> drwxr-xr-x. 2 elasticsearch elasticsearch 4096 May 10 01:00 _state
> drwxr-xr-x. 5 elasticsearch elasticsearch 4096 May 10 01:00 0
>
> /var/lib/elasticsearch/bigdatadev/nodes/0/indices/.marvel-2014.05.11:
>
> Any thoughts?
>
>
> On Tue, May 13, 2014 at 12:26 PM, deepakas [via ElasticSearch Users] <[hidden 
> email] <http://user/SendEmail.jtp?type=node&node=4055895&i=0>> wrote:
>
>> Hi Ivan/Boaz, 
>>
>> Thanks for the responses. I will checkout Curator. I already got the 
>> latest version of marvel last week using this command. 
>> bin/plugin -i elasticsearch/marvel/latest 
>>
>> Thanks, Deepak 
>>
>> ------------------------------
>>  If you reply to this email, your message will be added to the 
>> discussion below:
>>
>> http://elasticsearch-users.115913.n3.nabble.com/Marvel-Indices-taking-lot-of-space-Can-we-specify-automatic-delete-of-marvel-indice-tp4055729p4055784.html
>>  
>>  To unsubscribe from Marvel Indices taking lot of space ? Can we specify 
>> automatic delete of marvel indice ?, click here.
>> NAML<http://elasticsearch-users.115913.n3.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>>  
>>
>
>
>
> -- 
> Deepak Subhramanian 
>
> ------------------------------
> View this message in context: Re: Marvel Indices taking lot of space ? 
> Can we specify automatic delete of marvel indice 
> ?<http://elasticsearch-users.115913.n3.nabble.com/Marvel-Indices-taking-lot-of-space-Can-we-specify-automatic-delete-of-marvel-indice-tp4055729p4055895.html>
> Sent from the ElasticSearch Users mailing list 
> archive<http://elasticsearch-users.115913.n3.nabble.com/>at Nabble.com.
>

-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/36baa5ec-c467-47df-b597-0aee612dd888%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to