Index Optimization


The Optimize API (force merge API since ES v5.x) allows users to force merging of one or more indices through an API. The merge relates to the number of segments a Lucene index holds within each shard. The force merge operation allows the reduction in the number of segments by merging them.

More details:


Activate the index optimization process

# /opt/configurator/configure
Display only the mandatory entries? (Yn): n
Configure all the modules when finished? (Yn): n

UBIqube SOC Configuration Menu

1: System configuration
2: Web Portal configuration
3: JEntreprise configuration
4: SEC Engine configuration
5: Reports configuration
6: Database configuration
7: Alarms and events notifications
8: SOC Customisation
9: Zero Touch Deployment
10: OSS BSS third party tools integration
11: ElasticSearch configuration

0: save & exit (use CTRL-C to exit without saving)

ElasticSearch configuration

1: cluster configuration
2: Web portal (SES and JENTREPRISE)
3: SEC Engine

0: back

cluster configuration

1: general
2: network settings
3: retention policy
4: discovery
5: advanced config: breakers and gateway

0: back


1: name of the elasticsearch cluster for this node (DEV_ES_1622)
2: Version (5.6)
3: ID (integrer) of this elasticsearch node (STANDALONE)
4: set this node as a master node (true)
5: set this node as a data node (true)
6: set the number of shard (split) of an index (1)
7: set the number of replicas of an index. If the cluster is mono-node, this setting is irrelevant (0)
8: set the directory where Elasticsearch will store data (/opt/elasticsearch/data)
9: activate the daily index management script. This script will create the replica if needed, optimize the index... (true/false) (true)
10: set the minimum java heap size (2g)
11: set the maximum java heap size (2g)

Configure N-1, N-2 and N-3 index days with which the process will be launched


Concerned file: /opt/ubi-elasticsearch/index_management.php