Shulou(Shulou.com)06/01 Report--

Online ELK has been running for some time, but there are a variety of minor problems, logstash often hang up, kibana query is slow, and so on, now I have decided to upgrade the ELK component to the latest version to see the effect.

An upgrade of Elasticsearch

The original version of Elasticsearch is 1.7.1 and the latest version of Elasticsearch is 2.3.3.

The first thing to check before upgrading is the official document about the upgrade notes.

1. View Breaking Changes description

The general principles of Elasticsearch's upgrade are:

Large version upgrade requires restarting the entire Elasticsearch cluster

A small version upgrade can upgrade one cluster node at a time

As the version span of our upgrade is relatively large, we need to understand the version changes in detail.

two。 Use the elasticsearch-migration plug-in to help diagnose upgrades

The elasticsearch-migration plug-in can help check whether the current version can be upgraded directly to the next version, or whether some changes are made to existing data or clusters before upgrading.

Currently encountered a need to change, Elasticsearch3.0 can not be used after the belt "." Fields, such as nginx.client, can no longer be used and can be changed to nginx_clent.

Install plug-ins in the following versions of Elasticsearch3.0

. / bin/plugin-I migration-u https://github.com/elastic/elasticsearch-migration/releases/download/v1.18/elasticsearch-migration-1.18.zip

Through http://xxxx:9200/_plugin/migration/

This url access, and then follow the prompts

3. Back up data before upgrading

4. Upgrade the new version and restart the entire Elasticsearch

Pay attention to check the log during the upgrade to see if there is any error message, and search for the corresponding solution for each error message.

Second upgrade Logstash

Logstash upgraded from version 1.5.5 to 2.3.3

The new version adds some useful features, fixes some previous BUG, and you can check the official documentation for details.

Configuration files can be loaded dynamically

Starting with Logstash3.3, you can set up Logstash to automatically check and load configuration files

Bin/logstash-f apache.config-- auto-reload

By default, Logstash checks for configuration changes every 3 seconds. You can specify the interval between checks by-- reload-interval.

If you want to force a reload, you can use the SIGHHUP signal

Variables can be referenced in the configuration file

Input {tcp {port = > "${TCP_PORT:54321}"}}

Core components are rewritten with Java, resulting in improved performance

Use bin/logstash-plugin instead of bin/plugin

Third upgrade Kibana

Wget https://download.elastic.co/kibana/kibana/kibana-4.5.1-linux-x64.tar.gz

After the upgrade, there was no more alarm that logstash hung up.

Reference documentation:

Https://www.elastic.co/guide/en/elasticsearch/reference/2.3/setup-upgrade.html

Https://www.elastic.co/guide/en/elasticsearch/reference/2.3/breaking-changes.html

Https://github.com/elastic/logstash/blob/2.3/CHANGELOG.md#233-june-14-2016

Https://github.com/elastic/elasticsearch-migration/tree/1.x

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.