rooty/fab-manager
1
0
Fork 0
mirror of https://github.com/LaCasemate/fab-manager.git synced 2025-02-19 13:54:25 +01:00
Code Issues Releases Activity

improved ES upgrade doc

Browse Source
This commit is contained in:
Sylvain 2018-12-03 16:15:34 +01:00
parent fab1e4eb6b
commit aac40784ed
2 changed files with 9 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
CHANGELOG.md
View File

@ -4,6 +4,7 @@
- Prevent running elastic-upgrade script with wrong awk version
- Fix ElasticSearch upgrade script
- Setup ElasticSearch configuration files for new installations
- Improved ES upgrade documentation
# v2.7.3 2018 December 03

21
doc/elastic_upgrade.md
View File

@ -31,10 +31,10 @@ For instructions regarding a manual upgrade, please refer to the official docume
- https://www.elastic.co/guide/en/elasticsearch/reference/2.4/restart-upgrade.html
- https://www.elastic.co/guide/en/elasticsearch/reference/5.6/restart-upgrade.html
## Revert the upgrade
## Restart the upgrade
So something goes wrong and the upgrade was not successful.
Sad news, but everything isn't lost, follow this procedure to downgrade to ElasticSearch 1.7.
So something goes wrong and the upgrade failed during ES 2.4 reindexing?
Sad news, but everything isn't lost, follow this procedure to start the upgrade again.
First, check the status of your indices:
@ -56,13 +56,11 @@ green open fablab 5 0 1944 4 1.2mb 1.2m
Here, we can see that the migration is not complete, as *docs.count* are not equal for `stat_24` and `stats`.
Now let's stop and remove the ElasticSearch container.
Let's remove the bogus indices:
```bash
docker-compose stop elasticsearch
docker-compose rm -f elasticsearch
docker-compose down
curl -XDELETE "$ES_IP:9200/fablab_24"
curl -XDELETE "$ES_IP:9200/stats_24"
```
Then, edit your [docker-compose.yml](../docker/docker-compose.yml) and change the *elasticsearch* block according to the following:
@ -98,15 +96,12 @@ Then, edit your [docker-compose.yml](../docker/docker-compose.yml) and change th
</td></tr>
</table>
Restart your containers:
Now you can safely restart the upgrade script.
```bash
docker-compose pull
docker-compose up -d
\curl https://raw.githubusercontent.com/LaCasemate/fab-manager/master/scripts/elastic-upgrade.sh | bash
```
Now you're back with ElasticSearch 1.7. You can safely restart the upgrade script.
## Debugging the upgrade
You can check for any error during container startup, using: