You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Dec 14, 2022. It is now read-only.
Copy file name to clipboardExpand all lines: UPDATE.md
+8-5Lines changed: 8 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -124,12 +124,8 @@ The solution ships the latest available Elastic version with new releases. Howev
124
124
125
125
:exclamation: Before proceeding, make sure that your Elasticsearch cluster consists of __at least 3 nodes__. For example 3 Elasticsearch nodes running on two machines is perfectly fine for this.
126
126
There are 3 Elasticsearch nodes required, as there must always be a master node in the cluster. If this master node is stopped, a quorum of remaining cluster nodes must still be running to elect a new master, otherwise an upgraded Elasticsearch node cannot join the cluster. [Learn more](https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-discovery-quorums.html)
127
-
If you have 2 Elasticsearch nodes, then you can bring up another node using the following command:
128
127
129
-
```
130
-
docker-compose -f elasticsearch/docker-compose.es03.yml up -d
131
-
```
132
-
[Read more](README.md##general-remarks) information about adding additional cluster node. After the upgrade, you can remove the third cluster node if necessary. Before proceeding, make sure that Elasticsearch is in the Green state.
128
+
[Read more](README.md##general-remarks) information about adding additional cluster nodes. After the upgrade, you can remove the third cluster node if necessary. Before proceeding, make sure that Elasticsearch is in the Green state.
133
129
134
130
### Elastic stack upgrade steps
135
131
@@ -213,3 +209,10 @@ The solution ships a defined Elasticsearch version with each release, which is u
213
209
### Can I skip several versions for an upgrade?
214
210
215
211
Yes, you can. Please note which components have been updated between the current and the new version.
212
+
213
+
214
+
### Can I downgrade back to a previous version?
215
+
216
+
No, you cannot downgrade from a newer version to an older one. You will see the following error message:
217
+
`cannot downgrade a node from version [7.16.1] to version [7.15.2]`
218
+
Please note that as soon as a newer Elasticsearch node was started, the data stored on the volume was updated, which makes it impossible to start an older version.
0 commit comments