<commit_before>---
title: Upgrading from Previous Versions
aliases:
    - /enterprise/v1.3/administration/upgrading/
menu:
  enterprise_influxdb_1_3:
    weight: 0
    parent: Administration
---
## Upgrading from version 1.3.x to 1.3.7
Version 1.3.7 is a drop-in replacement for earlier releases of 1.3.x with no data migration required.

## Upgrading from version 1.2.5 to 1.3.x

Version 1.3.x introduces changes to the data node configuration file and there are changes to the 
underlying communication protocols between the nodes used for hinted handoff.

The impact of the hinted handoff protocol change means that you will be unable to perform a `downgrade` if there are
points contained within the hinted handoff queue of the upgraded nodes.  There are recommendations below which describe
how to avoid building up hinted handoff queue points while upgrading.

Please update that configuration file to avoid any unnecessary downtime.
The steps below outline the upgrade process and include a list of the required configuration changes.

### Step 0: Back up your cluster before upgrading to version 1.3.
It is recommended to create a full backup of your cluster prior to executing the upgrade. If you are 
already have incremental backups being created as part of your standard operating procedures, you should 
trigger a final incremental backup before proceeding with the upgrade.
<dt>
Note that you need to ensure you have sufficient disk space before triggering the backup.
</dt>
The following command uses the [version 1.2 backup syntax](https://docs.influxdata.com/enterprise_influxdb/v1.2/guides/backup-and-restore/#syntax) 
to create an incremental backup of your cluster and it stores that backup in the current directory.

```
influxd-ctl backup .
```

Otherwise, you should create a full backup before proceeding. 
The following command uses the [backup syntax originally introduced in version 1.2](https://docs.influxdata.com/enterprise_influxdb/v1.3/guides/backup-and-restore/#syntax) 
to create a full backup of your cluster and it stores that backup in the current directory. 

```
influxd-ctl backup -full .
```
You should start by upgrading the meta nodes first ensuring that the meta cluster is healthy, before proceeding to the
data nodes. 

### Repeat the following steps for each meta node in the cluster

### Step 1: Download the 1.3.7 meta node packages

#### Meta node package download
**Ubuntu & Debian (64-bit)**
```
wget https://dl.influxdata.com/enterprise/releases/influxdb-meta_1.3.7-c1.3.7_amd64.deb
```

**RedHat & CentOS (64-bit)**
```
wget https://dl.influxdata.com/enterprise/releases/influxdb-meta-1.3.7_c1.3.7.x86_64.rpm
```

### Step 2: Install the 1.3.7 meta nodes packages

#### Meta node package install

**Ubuntu & Debian (64-bit)**
```
sudo dpkg -i influxdb-meta_1.3.7-c1.3.7_amd64.deb
```

**RedHat & CentOS (64-bit)**
```
sudo yum localinstall influxdb-meta-1.3.7_c1.3.7.x86_64.rpm
```

### Step 3: Restart the influxdb-meta process

#### Meta node restart
**sysvinit systems**
```
service influxdb-meta restart
```
**systemd systems**
```
sudo systemctl restart influxdb-meta
```

### Step 4: Confirm the upgrade

Once you've performed the upgrade on ALL meta nodes, check your nodes' version numbers using the 
`influxd-ctl show` command.
The [`influxd-ctl` tool](/enterprise_influxdb/v1.3/features/cluster-commands/) is available on all meta nodes.

```
~# influxd-ctl show

Data Nodes
==========
ID	TCP Address		Version
4	rk-upgrading-01:8088	1.2.x_c1.2.y   
5	rk-upgrading-02:8088	1.2.x_c1.2.y
6	rk-upgrading-03:8088	1.2.x_c1.2.y

Meta Nodes
==========
TCP Address		Version
rk-upgrading-01:8091	1.3.7_c1.3.7   # 1.3.7_c1.3.7 = 👍
rk-upgrading-02:8091	1.3.7_c1.3.7
rk-upgrading-03:8091	1.3.7_c1.3.7
```

### Repeat the following steps for each data node in the cluster

### Step 1: Download the 1.3.7 data node packages

#### Data node package download
**Ubuntu & Debian (64-bit)**
```
wget https://dl.influxdata.com/enterprise/releases/influxdb-data_1.3.7-c1.3.7_amd64.deb
```

**RedHat & CentOS (64-bit)**
```
wget https://dl.influxdata.com/enterprise/releases/influxdb-data-1.3.7_c1.3.7.x86_64.rpm
```

### Step 2: Remove the data node from the load balancer

In order to avoid downtime and allow for a smooth transition, remove the data node that you plan to upgrade from your
load balancer prior to performing the remaining steps.

### Step 3: Install the 1.3.7 data node packages

#### 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.3.7.
Please keep your current configuration file by entering `N` or `O`;
we update the configuration file with the necessary changes for version 1.3.7 in step 3.

**Ubuntu & Debian (64-bit)**
```
sudo dpkg -i influxdb-data_1.3.7-c1.3.7_amd64.deb
```

**RedHat & CentOS (64-bit)**
```
sudo yum localinstall influxdb-data-1.3.7_c1.3.7.x86_64.rpm
```

### Step 4: Update the data node configuration file

Add:

* [index-version = "inmem"](/enterprise_influxdb/v1.3/administration/configuration/#index-version-inmem) to the `[data]` section
* [wal-fsync-delay = "0s"](/enterprise_influxdb/v1.3/administration/configuration/#wal-fsync-delay-0s) to the `[data]` section
* [max-concurrent-compactions = 0](/enterprise_influxdb/v1.3/administration/configuration/#max-concurrent-compactions-0) to the `[data]` section
* [pool-max-idle-streams = 100](/enterprise_influxdb/v1.3/administration/configuration/#pool-max-idle-streams-100) to the `[cluster]` section
* [pool-max-idle-time = "1m0s"](/enterprise_influxdb/v1.3/administration/configuration/#pool-max-idle-time-1m0s) to the `[cluster]` section
* the [[anti-entropy]](/enterprise_influxdb/v1.3/administration/configuration/#anti-entropy) section:
```
[anti-entropy]
  enabled = true
  check-interval = "30s"
  max-fetch = 10
```

Remove:

* `max-remote-write-connections` from the `[cluster]` section
* the [[admin]](/enterprise_influxdb/v1.3/administration/configuration/#admin) section

Update:

* [cache-max-memory-size](/enterprise_influxdb/v1.3/administration/configuration/#cache-max-memory-size-1073741824) to `1073741824` in the `[data]` section

The new configuration options are set to their default settings.
Follow the links for more information about those options.

### Step 5: Restart the influxdb process
<commit_msg>Update upgrading.md<commit_after>---
title: Upgrading from Previous Versions
aliases:
    - /enterprise/v1.3/administration/upgrading/
menu:
  enterprise_influxdb_1_3:
    weight: 0
    parent: Administration
---
## Upgrading from version 1.3.x to 1.3.7
Version 1.3.7 is a drop-in replacement for earlier releases of 1.3.x with no data migration required.

## Upgrading from version 1.2.5 to 1.3.x

Version 1.3.x introduces changes to the data node configuration file and there are changes to the 
underlying communication protocols between the nodes used for hinted handoff.

The impact of the hinted handoff protocol change means that you will be unable to perform a `downgrade` if there are
points contained within the hinted handoff queue of the upgraded nodes.  There are recommendations below which describe
how to avoid building up hinted handoff queue points while upgrading.

Please update that configuration file to avoid any unnecessary downtime.
The steps below outline the upgrade process and include a list of the required configuration changes.

### Step 0: Back up your cluster before upgrading to version 1.3.
It is recommended to create a full backup of your cluster prior to executing the upgrade. If you are 
already have incremental backups being created as part of your standard operating procedures, you should 
trigger a final incremental backup before proceeding with the upgrade.
<dt>
__NOTE:__ You need to ensure you have sufficient disk space before triggering the backup!
</dt>
The following command uses the [version 1.2 backup syntax](https://docs.influxdata.com/enterprise_influxdb/v1.2/guides/backup-and-restore/#syntax) 
to create an incremental backup of your cluster and it stores that backup in the current directory.

```
influxd-ctl backup .
```

Otherwise, you should create a full backup before proceeding. 
The following command uses the [backup syntax originally introduced in version 1.2](https://docs.influxdata.com/enterprise_influxdb/v1.3/guides/backup-and-restore/#syntax) 
to create a full backup of your cluster and it stores that backup in the current directory. 

```
influxd-ctl backup -full .
```
You should start by upgrading the meta nodes first ensuring that the meta cluster is healthy, before proceeding to the
data nodes. 

### Repeat the following steps for each meta node in the cluster

### Step 1: Download the 1.3.7 meta node packages

#### Meta node package download
**Ubuntu & Debian (64-bit)**
```
wget https://dl.influxdata.com/enterprise/releases/influxdb-meta_1.3.7-c1.3.7_amd64.deb
```

**RedHat & CentOS (64-bit)**
```
wget https://dl.influxdata.com/enterprise/releases/influxdb-meta-1.3.7_c1.3.7.x86_64.rpm
```

### Step 2: Install the 1.3.7 meta nodes packages

#### Meta node package install

**Ubuntu & Debian (64-bit)**
```
sudo dpkg -i influxdb-meta_1.3.7-c1.3.7_amd64.deb
```

**RedHat & CentOS (64-bit)**
```
sudo yum localinstall influxdb-meta-1.3.7_c1.3.7.x86_64.rpm
```

### Step 3: Restart the influxdb-meta process

#### Meta node restart
**sysvinit systems**
```
service influxdb-meta restart
```
**systemd systems**
```
sudo systemctl restart influxdb-meta
```

### Step 4: Confirm the upgrade

Once you've performed the upgrade on ALL meta nodes, check your nodes' version numbers using the 
`influxd-ctl show` command.
The [`influxd-ctl` tool](/enterprise_influxdb/v1.3/features/cluster-commands/) is available on all meta nodes.

```
~# influxd-ctl show

Data Nodes
==========
ID	TCP Address		Version
4	rk-upgrading-01:8088	1.2.x_c1.2.y   
5	rk-upgrading-02:8088	1.2.x_c1.2.y
6	rk-upgrading-03:8088	1.2.x_c1.2.y

Meta Nodes
==========
TCP Address		Version
rk-upgrading-01:8091	1.3.7_c1.3.7   # 1.3.7_c1.3.7 = 👍
rk-upgrading-02:8091	1.3.7_c1.3.7
rk-upgrading-03:8091	1.3.7_c1.3.7
```

### Repeat the following steps for each data node in the cluster

### Step 1: Download the 1.3.7 data node packages

#### Data node package download
**Ubuntu & Debian (64-bit)**
```
wget https://dl.influxdata.com/enterprise/releases/influxdb-data_1.3.7-c1.3.7_amd64.deb
```

**RedHat & CentOS (64-bit)**
```
wget https://dl.influxdata.com/enterprise/releases/influxdb-data-1.3.7_c1.3.7.x86_64.rpm
```

### Step 2: Remove the data node from the load balancer

In order to avoid downtime and allow for a smooth transition, remove the data node that you plan to upgrade from your
load balancer prior to performing the remaining steps.

### Step 3: Install the 1.3.7 data node packages

#### 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.3.7.
Please keep your current configuration file by entering `N` or `O`;
we update the configuration file with the necessary changes for version 1.3.7 in step 3.

**Ubuntu & Debian (64-bit)**
```
sudo dpkg -i influxdb-data_1.3.7-c1.3.7_amd64.deb
```

**RedHat & CentOS (64-bit)**
```
sudo yum localinstall influxdb-data-1.3.7_c1.3.7.x86_64.rpm
```

### Step 4: Update the data node configuration file

Add:

* [index-version = "inmem"](/enterprise_influxdb/v1.3/administration/configuration/#index-version-inmem) to the `[data]` section
* [wal-fsync-delay = "0s"](/enterprise_influxdb/v1.3/administration/configuration/#wal-fsync-delay-0s) to the `[data]` section
* [max-concurrent-compactions = 0](/enterprise_influxdb/v1.3/administration/configuration/#max-concurrent-compactions-0) to the `[data]` section
* [pool-max-idle-streams = 100](/enterprise_influxdb/v1.3/administration/configuration/#pool-max-idle-streams-100) to the `[cluster]` section
* [pool-max-idle-time = "1m0s"](/enterprise_influxdb/v1.3/administration/configuration/#pool-max-idle-time-1m0s) to the `[cluster]` section
* the [[anti-entropy]](/enterprise_influxdb/v1.3/administration/configuration/#anti-entropy) section:
```
[anti-entropy]
  enabled = true
  check-interval = "30s"
  max-fetch = 10
```

Remove:

* `max-remote-write-connections` from the `[cluster]` section
* the [[admin]](/enterprise_influxdb/v1.3/administration/configuration/#admin) section

Update:

* [cache-max-memory-size](/enterprise_influxdb/v1.3/administration/configuration/#cache-max-memory-size-1073741824) to `1073741824` in the `[data]` section

The new configuration options are set to their default settings.
Follow the links for more information about those options.

### Step 5: Restart the influxdb process

<dt>
**NOTE: As part of the changes associated with InfluxEnterprise 1.3, the hinted handoff queue is now segmented by node and
shard. See 
[Release Notes/Change Log](https://docs.influxdata.com/enterprise_influxdb/v1.3/about-the-project/release-notes-changelog/#v1-3-0-2017-06-21).  
As a result, when you restart data nodes, you will see log messages indicating that there is a "protocol" issue writing points 
from the hinted handoff queue between 1.2 and 1.3 nodes. These will resolve themselves once all of the dat nodes have been
upgraded.

As a result of this change, if you need to downgrade to 1.2 for any reason, you must halt inbound writes while you downgrade
the data nodes because the hinted handoff segmentation is not compatible from 1.3 to 1.2.  You can stop write traffic at the
load balancer, by removing ALL data nodes temporarily while you downgrade the binaries and configuration files.  See Step 2
above.
</dt>

{'fraction_non_alphanumeric': 0.1119159724737414, 'fraction_numerical': 0.04244838826512133, 'mean_word_length': 4.3866562621927425, 'pattern_counts': {'":': 0, '<': 9, '<?xml version=': 0, '>': 9, 'https://': 13, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 8, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '1085853', 'n_tokens_mistral': 4815, 'n_tokens_neox': 4382, 'n_words': 1526}