如何使用策展人从S3恢复弹性搜索索引到空白群？ [英] how to restore elasticsearch indices from S3 to blank cluster using curator?
问题描述
我在目标群集的es客户端上安装了cloud-aws插件，并且使用环境变量将权限设置为S3 bucket。我有配置和动作文件到位策展人。我已经验证了S3存储区的AWS权限，但是我不知道如何从弹性搜索集群的角度验证权限。当我尝试运行策展人工作时，我得到以下内容：
get_repository：662找不到存储库my-elk-snapshots。
我知道如果我直接使用弹性搜索，我需要创建一个对S3桶的引用，以便群集知道它。这是新鲜恢复的情况吗？我认为策展人使用弹性搜索集群在引擎盖下，但我对这种情况感到困惑，因为集群本质上是空白的。
p>如何将存储库添加到原始（源）集群？您需要使用确切的相同的步骤将存储库添加到新的（目标）集群。只有这样，存储库才能被新的集群读取。这就是为什么你得到了找不到存储库的消息。必须将其添加到新群集，以便快照可见，因此可以恢复。
I have an S3 bucket of elasticsearch snapshots created by a curator job. I want to be able to restore these indexes to a fresh cluster using the S3 bucket. The target elasticsearch cluster does not have access to the source elasticsearch cluster by design.
I've installed cloud-aws plugin on the es client for the target cluster and I set permissions to the S3 bucket using environment variables. I have the config and action file in place for curator. I've verified the AWS permissions to the S3 bucket, but I'm not sure how to verify the permissions from the elasticsearch cluster's perspective. When I try running the curator job I get the following:
get_repository:662 Repository my-elk-snapshots not found.
I know that if I were to use elasticsearch directly I would need to create a reference to the S3 bucket so that the cluster knows about it. Is this the case for a fresh restore? I think that curator uses the elasticsearch cluster under the hood, but I'm confused about this scenario since the cluster is essentially blank.
How did you add the repository to the original (source) cluster? You need to use the exact same steps to add the repository to the new (target) cluster. Only then will the repository be readable by the new cluster. That's why you're getting the "repository not found" message. It has to be added to the new cluster so that snapshots are visible, and therefore able to be restored.
这篇关于如何使用策展人从S3恢复弹性搜索索引到空白群？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
