Curator run correctly
Curator displays an error message indicating that it is incompatible with the latest version of Elasticsearch
Login root user
curator --config /root/.curator/curator.yml --dry-run /root/.curator/action.yml
CentOS Linux release 7.6.1810 (Core)
Curator 5.6.0
File curator.yml
client:
hosts: [ "elasticsearch-node1:9200", "elasticsearch-node2:9200" ]
url_prefix:
use_ssl: False
certificate:
client_cert:
client_key:
ssl_no_validate: False
http_auth:
timeout: 30
master_only: False
logging:
loglevel: INFO
logfile:
logformat: default
blacklist: ['elasticsearch', 'urllib3']>
File action.yml
actions:
1:
action: delete_indices
description: >-
Delete indices older than 3 months (based on index name). Ignore the error if the filter
does not result in an actionable list of indices (ignore_empty_list) and exit cleanly.
options:
ignore_empty_list: True
filters:
- filtertype: age
source: name
direction: older
timestring: '%Y.%m.%d'
unit: months
unit_count: 3>
This is a known issue. The development version (master branch) fully supports Elasticsearch 7.0. I needed to wait for elasticsearch-py v7 to be released so that I could release with that version. I still need to run tests against that, and after that passes, then I can release Curator 5.7 with Elasticsearch 7 support.
@untergeek thanks for the Info! Hope it will be ready soon, since we have the same issue wit ES 7.0.0.
PS: Would be cool if the version number could be the same as ES stack also on Curator :-)
Same issue here
@untergeek looks like elasticsearch-py was released: https://github.com/elastic/elasticsearch-py/releases/tag/7.0.0
Is this what you're waiting for or is there something else?
My wife had surgery. Slight delay on that account.
Hope all is well with your wife. Just let us know when this is available and where to get it... repo preferred ;)
Curator 5.7.0 is released and published to all repositories. Docs are in the process of being updated as I write this.
Thank you so much for the quick turnaround! :)
On Wed, Apr 24, 2019 at 2:39 PM Aaron Mildenstein notifications@github.com
wrote:
Closed #1380 https://github.com/elastic/curator/issues/1380.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/elastic/curator/issues/1380#event-2298576935, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ADJ3WGBOLFSZWNLQ2M4YWA3PSDHQVANCNFSM4HF7W57Q
.
--
David Breise
Etica, Inc.
[email protected]
760.705.4022
CONFIDENTIALITY NOTICE: The information contained in this transmission may
contain privileged and confidential information. It is intended only for
the use of the person(s) named above. If you are not the intended
recipient, please contact the sender by reply email and permanently
Most helpful comment
This is a known issue. The development version (master branch) fully supports Elasticsearch 7.0. I needed to wait for
elasticsearch-pyv7 to be released so that I could release with that version. I still need to run tests against that, and after that passes, then I can release Curator 5.7 with Elasticsearch 7 support.