docs/_docs/installation/upgrades.adoc - ignite - Git at Google

 // Licensed to the Apache Software Foundation (ASF) under one or more
 // contributor license agreements.  See the NOTICE file distributed with
 // this work for additional information regarding copyright ownership.
 // The ASF licenses this file to You under the Apache License, Version 2.0
 // (the "License"); you may not use this file except in compliance with
 // the License.  You may obtain a copy of the License at
 //
 // http://www.apache.org/licenses/LICENSE-2.0
 //
 // Unless required by applicable law or agreed to in writing, software
 // distributed under the License is distributed on an "AS IS" BASIS,
 // WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 // See the License for the specific language governing permissions and
 // limitations under the License.
 = Version Upgrade

 Upgrade is an important part of the lifecycle of any software system. This page covers the basic recommendations for upgrading the Apache Ignite version.

 == Upgrading Nodes

 Updating node version is as simple as replacing the Apache Ignite binaries with a new version. However, there are several things to keep in mind when performing the upgrade:

 - Ignite cluster cannot have nodes that run on different Ignite versions. You need to stop the cluster and start it again on the new Ignite version.
 - It is possible to accidentally overwrite your persistent storage or other important data during the upgrade. It is recommended to move this data outside of intallation folder if you are planning upgrades:
 * The work directory is used to store application data and all data required for the node to work. You can change its location as described in tge link:setup#configuring-work-directory[Configuring Work Directory] section.
 * The persistent storage holds all information stored on the node. You can change its location as described in the link:persistence/native-persistence#configuring-persistent-storage-directory[Configuring Persistent Storage Directory] section.
 * WAL Archive os used to store WAL segments for recovery. You can change its location as described in link:persistence/native-persistence#wal-archive[WAL Archive] section.
	// Licensed to the Apache Software Foundation (ASF) under one or more
	// contributor license agreements. See the NOTICE file distributed with
	// this work for additional information regarding copyright ownership.
	// The ASF licenses this file to You under the Apache License, Version 2.0
	// (the "License"); you may not use this file except in compliance with
	// the License. You may obtain a copy of the License at
	//
	// http://www.apache.org/licenses/LICENSE-2.0
	//
	// Unless required by applicable law or agreed to in writing, software
	// distributed under the License is distributed on an "AS IS" BASIS,
	// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
	// See the License for the specific language governing permissions and
	// limitations under the License.
	= Version Upgrade

	Upgrade is an important part of the lifecycle of any software system. This page covers the basic recommendations for upgrading the Apache Ignite version.

	== Upgrading Nodes

	Updating node version is as simple as replacing the Apache Ignite binaries with a new version. However, there are several things to keep in mind when performing the upgrade:

	- Ignite cluster cannot have nodes that run on different Ignite versions. You need to stop the cluster and start it again on the new Ignite version.
	- It is possible to accidentally overwrite your persistent storage or other important data during the upgrade. It is recommended to move this data outside of intallation folder if you are planning upgrades:
	* The work directory is used to store application data and all data required for the node to work. You can change its location as described in tge link:setup#configuring-work-directory[Configuring Work Directory] section.
	* The persistent storage holds all information stored on the node. You can change its location as described in the link:persistence/native-persistence#configuring-persistent-storage-directory[Configuring Persistent Storage Directory] section.
	* WAL Archive os used to store WAL segments for recovery. You can change its location as described in link:persistence/native-persistence#wal-archive[WAL Archive] section.