ES报错:Can not be imported as a dangling index as index with same name already exists in cluster me
2017-12-01 00:59
3871 查看
解决方案:
你不应该直接删除报警日志中的.kibana index,因为可能会因此在kibana中丢失数据。假如你曾经删除过 .kibana indice,那么这个警告就是你过去那个删除操作的残留结果。
相应地,你应该知道操作的危险性:
kibana官方配置文档
https://www.elastic.co/guide/en/kibana/current/settings.html
默认情况:kibana会 使用es的索引去存储保存的搜索,可视化界面,kibana可以创建一个之前不存在的索引。
在node上的错说的是,你有一个目录在data/node/x/indices/xxx中,它与
indices .kibana 以不识别的id关联。所以es不知道为什么这个文件会在这里,es忽略它,并抛出警告。
假如你确认你要在某一刻去删除它,你应该知道index目前的id已经改变才行,如果你乐于在目前的index里看到的都是正确的信息,想去清理掉及经常出现的报警信息,那你就去删除那个报警日志中那个特殊节点上的特殊目录,每一个这样的操作,你必须确保你仅仅移动或删除的是正确的目录(这个目录包含这个特殊节点的重复创建的不必要的数据信息)。
你不应该直接删除报警日志中的.kibana index,因为可能会因此在kibana中丢失数据。假如你曾经删除过 .kibana indice,那么这个警告就是你过去那个删除操作的残留结果。
相应地,你应该知道操作的危险性:
kibana官方配置文档
https://www.elastic.co/guide/en/kibana/current/settings.html
默认情况:kibana会 使用es的索引去存储保存的搜索,可视化界面,kibana可以创建一个之前不存在的索引。
在node上的错说的是,你有一个目录在data/node/x/indices/xxx中,它与
indices .kibana 以不识别的id关联。所以es不知道为什么这个文件会在这里,es忽略它,并抛出警告。
假如你确认你要在某一刻去删除它,你应该知道index目前的id已经改变才行,如果你乐于在目前的index里看到的都是正确的信息,想去清理掉及经常出现的报警信息,那你就去删除那个报警日志中那个特殊节点上的特殊目录,每一个这样的操作,你必须确保你仅仅移动或删除的是正确的目录(这个目录包含这个特殊节点的重复创建的不必要的数据信息)。
相关文章推荐
- ES报错:Can not be imported as a dangling index as index with same name already exists in cluster me
- Deprecated: Methods with the same name as their class will not be constructors in a future version o
- Deprecated: Methods with the same name as their class will not be constructors in a future version of PHP
- ES报错dangling index, exists on local file system, but not in cluster metadata, auto import to cluster
- Deprecated: Methods with the same name as their class will not be constructors in a future version
- Ehcache依赖版本问题:Another CacheManager with same name 'es' already exists in the same VM.
- This platform could not be created because a solution platform of the same name already exists.
- [PHP] Deprecated: Methods with the same name as their class will not be constructor...
- The virtual machine could not be added. The virtual machine configuration could not be added. A configuration with this name already exists.
- This platform could not be created because a solution platform of the same name already exists解决方法
- Can not find a java.io.InputStream with the name [downloadFile] in the invocation stack问题解决
- AS 中报错:Error:(22, 0) Project with path ':library' could not be found in project ':indict
- Excel导入遇到的问题An object with the same key already exists in the ObjectStateManager……
- Struts2 下载 Can not find a java.io.InputStream with the name [downloadFile] in the invocation stack
- (文件下载)Can not find a java.io.InputStream with the name [inputStream] in the invocation stack
- strut2下载时候的一种异常 Can not find a java.io.InputStream with the name [inputStream] in the invocation stack
- A new node couldn't be inserted because one with the same name exists. (VERR_CFGM_NODE_EXISTS)
- Only one expression can be specified in the select list when the subquery is not introduced with(求助)
- struts2文件的下载,Can not find a java.io.InputStream with the name [inputStream] in the invocation stack. Check the tag specified
- Error applying site theme: A theme with the name "Jet 1011" and version already exists on the server.