Elasticsearch data isn't purged when it expires

Bug #1616765 reported by Simon Pasquier on 2016-08-25
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
StackLight
High
Simon Pasquier
0.10
Undecided
Simon Pasquier

Bug Description

Applies to StackLight 0.10.0 with MOS 8/9.

The Curator version that ships with the plugin doesn't support Elasticsearch 2.x:

2016-08-23 02:00:01,374 DEBUG curator.cli.utils check_version:90 Detected Elasticsearch version 2.3.3
Expected Elasticsearch version range > 1.0.0 < 2.0.0
ERROR: Incompatible with version 2.3.3 of Elasticsearch. Exiting.

Fix proposed to branch: master
Review: https://review.openstack.org/360401

Changed in lma-toolchain:
assignee: LMA-Toolchain Fuel Plugins (mos-lma-toolchain) → Simon Pasquier (simon-pasquier)
status: Triaged → In Progress
Simon Pasquier (simon-pasquier) wrote :

Workaround for 0.10.0 installations
===================================

on every Elasticsearch node, run the following snippet:

http://paste.openstack.org/show/563395/

By default the curator job is executed every day at 2am. If you want to run it immediatly, use this command:
$(crontab -l | grep 'delete indices' | sed 's/0 2 \* \* \* //' | sed 's/\\%/%/g')

Reviewed: https://review.openstack.org/360401
Committed: https://git.openstack.org/cgit/openstack/fuel-plugin-elasticsearch-kibana/commit/?id=c0794133d68bc7a9031c0432ba95098ba5ffced2
Submitter: Jenkins
Branch: master

commit c0794133d68bc7a9031c0432ba95098ba5ffced2
Author: Simon Pasquier <email address hidden>
Date: Thu Aug 25 11:50:55 2016 +0200

    Fix Elasticsearch curator job

    This change upgrades the version of elasticsearch-curator because the
    previous version (3.3.0) doesn't support Elasticsearch 2.x. As a
    consequence, data older than the defined retention period was never
    removed from Elasticsearch.

    The curator is now installed on all the Elasticsearch nodes (previously
    only on the primary node) and by configuration, it will only be
    executed on the ES cluster master node.

    Change-Id: I9da9e67fa4d353e78bd752456a9b01ca1fbae704
    Closes-Bug: #1616765
    Related-Bug: #1602719

Changed in lma-toolchain:
status: In Progress → Fix Committed

Reviewed: https://review.openstack.org/362263
Committed: https://git.openstack.org/cgit/openstack/fuel-plugin-elasticsearch-kibana/commit/?id=6047e4f8c1e1d332fc92efa520f210f687f8ecd8
Submitter: Jenkins
Branch: stable/0.10

commit 6047e4f8c1e1d332fc92efa520f210f687f8ecd8
Author: Simon Pasquier <email address hidden>
Date: Thu Aug 25 11:50:55 2016 +0200

    Fix Elasticsearch curator job

    This change upgrades the version of elasticsearch-curator because the
    previous version (3.3.0) doesn't support Elasticsearch 2.x. As a
    consequence, data older than the defined retention period was never
    removed from Elasticsearch.

    The curator is now installed on all the Elasticsearch nodes (previously
    only on the primary node) and by configuration, it will only be
    executed on the ES cluster master node.

    Conflicts:
     deployment_scripts/puppet/manifests/provision_services.pp

    Change-Id: I9da9e67fa4d353e78bd752456a9b01ca1fbae704
    Closes-Bug: #1616765
    Related-Bug: #1602719
    (cherry picked from commit c0794133d68bc7a9031c0432ba95098ba5ffced2)

Changed in lma-toolchain:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers