On Wednesday, May 06, 2015 at 07:09 CEST,
sumeet dembra <sumeetdem...@gmail.com> wrote:
> That is what I am not getting.
> Why is it showing 2014.00.28?
> There is no such index present inÂ
> my ES setup which has dateÂ
> 2014.00.28..
Looking at the code I suspect you have a snapshot or an index with that
name. The exception happens in timestamp_check[0] which is only called
from apply_filter[1]. apply_filter is, in turn, called from [2] and [3].
Upping the loglevel to 'debug' will cause the list being filtered to be
logged.
[0] https://github.com/elastic/curator/blob/v3.0.3/curator/api/filter.py#L285
[1] https://github.com/elastic/curator/blob/v3.0.3/curator/api/filter.py#L127
[2]
https://github.com/elastic/curator/blob/v3.0.3/curator/cli/snapshot_selection.py#L74
[3]
https://github.com/elastic/curator/blob/v3.0.3/curator/cli/index_selection.py#L80
--
Magnus Bäck | Software Engineer, Development Tools
magnus.b...@sonymobile.com | Sony Mobile Communications
--
Please update your bookmarks! We moved to 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+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/20150506074757.GA16989%40seldlx20533.corpusers.net.
For more options, visit https://groups.google.com/d/optout.
