升级Elasticsearch 2.1.1至2.2.0 - 缺少身份验证令牌？

Question

我决定尝试将当前群集从ES2.1.1升级到ES2.2.0。 镜像对。群集在AWS内运行，因此我使用cloud-aws插件进行通信。

我成功升级了第一个节点，并且它已经承担了主站状态，但升级第二个节点时遇到了一个奇怪的通信/身份验证问题。

我注意到指南here，但我似乎仍然遇到一个奇怪的问题。

从第二个节点上主群集日志：

[2016-02-03 12:29:41,241][INFO ][discovery.ec2   ] [Sharon Ventura] failed to send join request to master [{Space Phantom}{NzN7b7ZHT8uPu6oXJAORMg}{10.60.164.147}{10.60.164.147:9300}], reason [RemoteTransportException[[Space Phantom][10.60.164.147:9300][internal:discovery/zen/join]]; nested: IllegalStateException[failure when sending a validation request to node]; nested: RemoteTransportException[[Sharon Ventura][10.60.163.74:9300][internal:discovery/zen/join/validate]]; nested: ElasticsearchSecurityException[missing authentication token for action [internal:discovery/zen/join/validate]]; ] 
[2016-02-03 12:29:42,455][DEBUG][action.admin.cluster.health] [Sharon Ventura] no known master node, scheduling a retry 
[2016-02-03 12:29:44,255][INFO ][discovery.ec2   ] [Sharon Ventura] failed to send join request to master [{Space Phantom}{NzN7b7ZHT8uPu6oXJAORMg}{10.60.164.147}{10.60.164.147:9300}], reason [RemoteTransportException[[Space Phantom][10.60.164.147:9300][internal:discovery/zen/join]]; nested: IllegalStateException[failure when sending a validation request to node]; nested: RemoteTransportException[[Sharon Ventura][10.60.163.74:9300][internal:discovery/zen/join/validate]]; nested: ElasticsearchSecurityException[missing authentication token for action [internal:discovery/zen/join/validate]]; ] 
[2016-02-03 12:29:47,269][INFO ][discovery.ec2   ] [Sharon Ventura] failed to send join request to master [{Space Phantom}{NzN7b7ZHT8uPu6oXJAORMg}{10.60.164.147}{10.60.164.147:9300}], reason [RemoteTransportException[[Space Phantom][10.60.164.147:9300][internal:discovery/zen/join]]; nested: IllegalStateException[failure when sending a validation request to node]; nested: RemoteTransportException[[Sharon Ventura][10.60.163.74:9300][internal:discovery/zen/join/validate]]; nested: ElasticsearchSecurityException[missing authentication token for action [internal:discovery/zen/join/validate]]; ] 
[2016-02-03 12:29:49,472][DEBUG][action.admin.cluster.state] [Sharon Ventura] timed out while retrying [cluster:monitor/state] after failure (timeout [30s]) 
[2016-02-03 12:29:49,473][INFO ][rest.suppressed   ] /_cluster/settings Params: {} 
MasterNotDiscoveredException[null] 
     at org.elasticsearch.action.support.master.TransportMasterNodeAction$AsyncSingleAction$5.onTimeout(TransportMasterNodeAction.java:205) 
     at org.elasticsearch.cluster.ClusterStateObserver$ObserverClusterStateListener.onTimeout(ClusterStateObserver.java:239) 
     at org.elasticsearch.cluster.service.InternalClusterService$NotifyTimeout.run(InternalClusterService.java:794) 
     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) 
     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) 
     at java.lang.Thread.run(Thread.java:745) 
[2016-02-03 12:29:50,283][INFO ][discovery.ec2   ] [Sharon Ventura] failed to send join request to master [{Space Phantom}{NzN7b7ZHT8uPu6oXJAORMg}{10.60.164.147}{10.60.164.147:9300}], reason [RemoteTransportException[[Space Phantom][10.60.164.147:9300][internal:discovery/zen/join]]; nested: IllegalStateException[failure when sending a validation request to node]; nested: RemoteTransportException[[Sharon Ventura][10.60.163.74:9300][internal:discovery/zen/join/validate]]; nested: ElasticsearchSecurityException[missing authentication token for action [internal:discovery/zen/join/validate]]; ] 

我elasticsearch.yml文件：

cluster.name: cluster01 
http.cors.enabled: true 
network.host: 0.0.0.0 
discovery.type: ec2 
discovery.ec2.tag.project_code_info: "cluster01" 
cloud.aws.region: eu-central-1 

我可以在它检测到的第一个节点的日志中看到：它有[Space Phantom][10.60.164.147:9300] 检测到它没有任何干预，但它显然无法验证。

我怀疑这可能与Shield插件有关，该插件也已安装，但正确和相同的权限设置与以前相同。没有其他变化。

我在屏蔽中使用用户名和密码，没有配置SSL。

任何人都可以协助吗？

Answer 1

我设法弄清楚了，如@ user3458016所要求的。

我设法解决重置所有设置和配置，删除插件license，shield，删除所有用户和以前一样重新添加所有的人（所有节点上）这个问题，通过。这些配置在开始时是相同的，所以这很奇怪。

首先，停止所有节点上的elasticsearch。 如果本地运行，停止kibana。

如果您有任何自定义角色，检查该配置在/etc/elasticsearch/shield/roles.yml如果可能的话 从单一记录的配置刷新此。

删除插件：

/usr/share/elasticsearch/bin/plugin remove elasticsearch/license/latest /usr/share/elasticsearch/bin/plugin remove elasticsearch/shield/latest

删除用户：

/usr/share/elasticsearch/bin/shield/esusers userdel admin /usr/share/elasticsearch/bin/shield/esusers userdel logstash

重新添加插件：

/usr/share/elasticsearch/bin/plugin install elasticsearch/license/latest -b /usr/share/elasticsearch/bin/plugin install elasticsearch/shield/latest -b

再添加用户：

/usr/share/elasticsearch/bin/shield/esusers useradd admin -p adminuserpw -r admin /usr/share/elasticsearch/bin/shield/esusers useradd logstash -p logstashuserpw -r logstash

如果您有任何自定义角色，仔细检查/etc/elasticsearch/shield/roles.yml的这个配置验证配置没有被修改或以上-书面。

开始弹性搜索第一个节点。 如果本地运行，则启动kibana。

检查指标已正确提出并且验证主节点状态。

在所有其他节点上执行上述所有步骤。其余节点上

开始elasticsearch，一次一个。 在开始下一个节点之前验证健康的群集复制。

我希望有人认为这有用。