From 5b9da548a0c8b4b0bceb1007583d24967ddda4a7 Mon Sep 17 00:00:00 2001 From: Robert Kaussow Date: Mon, 25 Jul 2022 09:01:38 +0200 Subject: [PATCH] chore: fix spellcheck --- .../2022/how-to-not-migrate-graylog-to-opensearch/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/posts/2022/how-to-not-migrate-graylog-to-opensearch/index.md b/content/posts/2022/how-to-not-migrate-graylog-to-opensearch/index.md index 3d4bd1b..cf35b1e 100644 --- a/content/posts/2022/how-to-not-migrate-graylog-to-opensearch/index.md +++ b/content/posts/2022/how-to-not-migrate-graylog-to-opensearch/index.md @@ -23,7 +23,7 @@ Fortunately, [Graylog](https://docs.graylog.org/) also knows this and recommends . As you usually don't wants to operate software that no longer receives security updates, I have started to look into a migration and prepared the Container and Ansible setup. My fist mistake on this journey was to believe I can just use the latest Opensearch (OS) release. Had I read the documentation [^graylog] more carefully I would have saved myself a lot of trouble... -Anyway, the actual migration of the cluster from ES v7.10 to OS v2.1 succeeded surprisingly smoothly. Well, almost, after all I had to rewrite the complete Ansible role because OS 2.x has changed almost all configuration parameters and API calls :tada: But as you can imagine, everything explodes while trying to start Graylog again. Dang. Just downgrading Opensearch was also not possible as the cluster and all indices were migrated successfully already. To get it back in a working state I decided to reset the entire cluster and restore the snapshots from the S3 backup repository before I start to start a next try, this time with a supported OS 1.x version :fingers_crossed: At least I have already completed the ES disaster recovery test for this year. +Anyway, the actual migration of the cluster from ES v7.10 to OS v2.1 succeeded surprisingly smoothly. Well, almost, after all I had to rewrite the complete Ansible role because OS 2.x has changed almost all configuration parameters and API calls :tada: But as you can imagine, everything explodes while trying to start Graylog again. Dang. Just downgrading Opensearch was also not possible as the cluster and all indices were migrated successfully already. To get it back in a working state I decided to reset the entire cluster and restore the snapshots from the S3 backup repository before I start to start a next try, this time with a supported OS 1.x version :fingers_crossed: At least I have already completed the ES disaster recovery test for this year. Lessons Learned: