Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1686925 - [RFE] Curator in OCP does not support reindex of indices
Summary: [RFE] Curator in OCP does not support reindex of indices
Keywords:
Status: NEW
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: RFE
Version: 3.11.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Paul Weil
QA Contact: Xiaoli Tian
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-08 16:43 UTC by Radomir Ludva
Modified: 2019-03-11 14:28 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:


Attachments (Terms of Use)

Description Radomir Ludva 2019-03-08 16:43:03 UTC
Description of problem:
After changing environment variables PRIMARY_SHARDS and REPLICA_SHARDS of the Elasticsearch deployment config old indices are still using the old values for shards.

Steps to Reproduce:
1. Install OCP cluster with logging and a specific number of shards and replicas for Elasticsearch.
2. Edit deployment config of Elasticsearch pod and change variables PRIMARY_SHARDS and REPLICA_SHARDS.
3. New pods for Elasticsearch are created but old indices are still using the old values.

Actual results:
It is not possible to use curator to reindex indices.

Expected results:
It is possible to use curator to reindex indices.

Additional info:
Currently, we can use curator only for deleting old logs. But curator can be also used to reindex indices. Using curator seems a lot safer than making a direct call to the reindex API manually.
https://www.elastic.co/guide/en/elasticsearch/client/curator/current/reindex.html


Note You need to log in before you can comment on or make changes to this bug.