简体   繁体   English

Amazon Elasticsearch 服务 Kibana 的错误:“租户索引迁移失败”

[英]Amazon Elasticsearch service Kibana's error: “Tenant indices migration failed”

I got my Elasticsearch service disk storage space totally used, henceforth I had to increase the space, which worked.我的Elasticsearch服务磁盘存储空间已完全使用,因此我不得不增加空间,这有效。 However, after that kibana stopped working with error on kibana URL as Tenant indices migration failed .但是,在那之后kibana停止工作,在 kibana URL 上出现错误,因为Tenant indices migration failed

I've tried multiple links but most of them are pointing towards opendistro related settings which I am not able to access in this case as my configuration is over Amazon Elasticsearch service .我尝试了多个链接,但其中大多数都指向与opendistro相关的设置,在这种情况下我无法访问,因为我的配置超过了Amazon Elasticsearch service One of the closest issue is About “Tenant indices migration failed” error in kibana最接近的问题之一是关于 kibana 中的“租户索引迁移失败”错误

Below is the screenshot from my kibana:下面是我的kibana的截图: 在此处输入图像描述

Any help will be highly appreciated.任何帮助将不胜感激。 Thanks in Advance.提前致谢。

I've got a workaround for Amazon's Elasticsearch which worked for me for the time being, and may help others as well who are facing the same problem with this service in future until fix is finally added to AWS , I've added the step below:我有一个亚马逊的Elasticsearch的解决方法,它暂时对我有用,并且可能会帮助其他在未来面临同样问题的人,直到最终将修复添加到AWS ,我添加了下面的步骤:

  1. Once you encounter this error, wait for your nodes(data nodes, if dedicated nodes are present) to be active.一旦遇到此错误,请等待您的节点(数据节点,如果存在专用节点)处于活动状态。
  2. Click on Edit domain in Elasticsearch service page on AWS.单击 AWS 上 Elasticsearch 服务页面中的Edit domain
  3. Change EBS storage size per node by 1GB ( this will cause migrations to happen again and possibly fix indices migration error ).每个节点的 EBS 存储大小更改 1GB(这将导致再次发生迁移并可能修复索引迁移错误)。
  4. Click Submit , and wait for domain to become active, once active try testing kibana url.点击Submit ,等待域激活,激活后尝试测试 kibana url。
  5. If it does not work try changing EBS storage size per node by 1GB again.如果它不起作用,请尝试再次将每个节点的 EBS 存储大小更改 1GB。
  6. Last resort to be try changing Instance type and again after domain is active switch to previous type.最后的手段是尝试更改实例类型,并在域处于活动状态后再次切换到以前的类型。

I've got this working solution by trial and error only.我只是通过反复试验得到了这个可行的解决方案。 I am open for discussion on the same.我愿意就此进行讨论。

I was running Kibana in Docker, so in my case I used this environment variable in my docker-compose :我在 Docker 中运行 Kibana,所以在我的情况下,我在docker-compose中使用了这个环境变量:

environment:
  - OPENDISTRO_SECURITY_MULTITENANCY_ENABLED=false

Reference: https://github.com/opendistro-for-elasticsearch/security-kibana-plugin/issues/102参考: https://github.com/opendistro-for-elasticsearch/security-kibana-plugin/issues/102

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM