This is archived documentation for InfluxData product versions that are no longer maintained. For newer documentation, see the latest InfluxData documentation.
Upgrading from version 1.1 to 1.2.5
Version 1.2.5 is a drop-in replacement for version 1.1.x with no data migration required.
Version 1.2.5 introduces changes to the meta node configuration file and the data node configuration file. Please update the configuration files prior to upgrading to avoid any unnecessary downtime. The steps below outline the upgrade process and include a list of the required configuration changes.
Step 1: Download the 1.2.5 packages
Meta node package download
Ubuntu & Debian (64-bit)
wget https://dl.influxdata.com/enterprise/releases/influxdb-meta_1.2.4-c1.2.5_amd64.deb
RedHat & CentOS (64-bit)
wget https://dl.influxdata.com/enterprise/releases/influxdb-meta-1.2.4_c1.2.5.x86_64.rpm
Data node package download
Ubuntu & Debian (64-bit)
wget https://dl.influxdata.com/enterprise/releases/influxdb-data_1.2.4-c1.2.5_amd64.deb
RedHat & CentOS (64-bit)
wget https://dl.influxdata.com/enterprise/releases/influxdb-data-1.2.4_c1.2.5.x86_64.rpm
Step 2: Install the 1.2.5 packages
Meta node package Install
When you run the install command, your terminal asks if you’d like to keep your current configuration file or overwrite your current configuration file with the file for version 1.2.5.
Please keep your current configuration file by entering N
or O
;
we update the configuration file with the necessary changes for version 1.2.5 in step 3.
Ubuntu & Debian (64-bit)
sudo dpkg -i influxdb-meta_1.2.4-c1.2.5_amd64.deb
RedHat & CentOS (64-bit)
sudo yum localinstall influxdb-meta-1.2.4_c1.2.5.x86_64.rpm
Data node package install
When you run the install command, your terminal asks if you’d like to keep your current configuration file or overwrite your current configuration file with the file for version 1.2.5.
Please keep your current configuration file by entering N
or O
;
we update the configuration file with the necessary changes for version 1.2.5 in step 3.
Ubuntu & Debian (64-bit)
sudo dpkg -i influxdb-data_1.2.4-c1.2.5_amd64.deb
RedHat & CentOS (64-bit)
sudo yum localinstall influxdb-data-1.2.4_c1.2.5.x86_64.rpm
Step 3: Update the meta node configuration file
The configuration options in this section are not new to version 1.2.5. They were, however, missing from the sample configuration file (
/etc/influxdb/influxdb-meta.conf
) in version 1.1.x.
In the [meta]
section of the configuration file (/etc/influxdb/influxdb-meta.conf
), add the following options:
Those configuration options are set to their default settings. Follow the links for more information about those options.
Step 4: Update the data node configuration file
Most of the configuration options in this section are not new to version 1.2.5. They were, however, missing from the sample configuration file (
/etc/influxdb/influxdb.conf
) in version 1.1.x. The only actual configuration changes between version 1.1.1 and version 1.2.5 are:
shard-writer-timeout
is removed from the[cluster]
section; the system now internally setsshard-writer-timeout
max-row-limit
in the[http]
section is set to0
by default instead of10000
Uncomment all commented section headers: [cluster]
, [retention]
, [shard-precreation]
, [admin]
, [monitor]
, [subscriber]
, [http]
, [[graphite]]
, [[collectd]]
, [[opentsdb]]
, [[udp]]
, and [[continuous_queries]]
.
That change ensures that any future configuration changes to those sections will take effect upon a restart with no additional steps.
Under the hostname
option at the top of the configuration file (/etc/influxdb/influxdb.conf
), add gossip-frequency = “3s”.
In the [meta]
section, add:
In the [monitor]
section, add remote-collect-interval = “10s”.
In the [[collectd]]
section, add:
In the [http] section
, change:
max-row-limit = 10000
to max-row-limit = 0
In the [[udp]]
section, add precision = “”.
In the [cluster]
section, remove shard-writer-timeout = “5s”.
The added configuration options are set to their default settings. Follow the links for more information about those options.
Step 5: Restart the processes
Meta node restart
sysvinit systems
service influxdb-meta restart
systemd systems
sudo systemctl restart influxdb-meta
Data node Restart
sysvinit systems
service influxdb restart
systemd systems
sudo systemctl restart influxdb
Step 6: Confirm the upgrade
Check your nodes’ version numbers using the influxd-ctl show
command.
The influxd-ctl
tool is available on all meta nodes.
~# influxd-ctl show
Data Nodes
==========
ID TCP Address Version
4 rk-upgrading-01:8088 1.2.4_c1.2.5 # 1.2.4_c1.2.5 = 👍
5 rk-upgrading-02:8088 1.2.4_c1.2.5
6 rk-upgrading-03:8088 1.2.4_c1.2.5
Meta Nodes
==========
TCP Address Version
rk-upgrading-01:8091 1.2.4_c1.2.5
rk-upgrading-02:8091 1.2.4_c1.2.5
rk-upgrading-03:8091 1.2.4_c1.2.5
If you have any issues upgrading your cluster, please do not hesitate to contact support at the email provided to you when you received your InfluxEnterprise license.