Solr的问题：CLUSTERSTATE说，我们是领导者，但我们本地不这么认为 [英] Solr issue: ClusterState says we are the leader, but locally we don't think so

问题描述

所以今天我们碰到一个令人不安的Solr的问题。
碎片的整个集群之一，重新启动之后不再是能够索引/存储文档。
我们没有对这个问题的提示，直到我们开始索引（查询服务器看起来很好）。
该错误是：

So today we run into a disturbing solr issue. After a restart of the whole cluster one of the shard stop being able to index/store documents. We had no hint about the issue until we started indexing (querying the server looks fine). The error is:

2014-05-19 18:36:20,707 ERROR o.a.s.u.p.DistributedUpdateProcessor [qtp406017988-19] ClusterState says we are the leader, but locally we don't think so
2014-05-19 18:36:20,709 ERROR o.a.s.c.SolrException [qtp406017988-19] org.apache.solr.common.SolrException: ClusterState says we are the leader     (http://x.x.x.x:7070/solr/shard3_replica1), but locally we don't think so. Request came from null
  at org.apache.solr.update.processor.DistributedUpdateProcessor.doDefensiveChecks(DistributedUpdateProcessor.java:503)
  at org.apache.solr.update.processor.DistributedUpdateProcessor.setupRequest(DistributedUpdateProcessor.java:267)
  at org.apache.solr.update.processor.DistributedUpdateProcessor.processAdd(DistributedUpdateProcessor.java:550)
  at org.apache.solr.handler.loader.JsonLoader$SingleThreadedJsonLoader.processUpdate(JsonLoader.java:126)
  at org.apache.solr.handler.loader.JsonLoader$SingleThreadedJsonLoader.load(JsonLoader.java:101)
  at org.apache.solr.handler.loader.JsonLoader.load(JsonLoader.java:65)
  at org.apache.solr.handler.UpdateRequestHandler$1.load(UpdateRequestHandler.java:92)
  at org.apache.solr.handler.ContentStreamHandlerBase.handleRequestBody(ContentStreamHandlerBase.java:74)
  at org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:135)
  at org.apache.solr.core.SolrCore.execute(SolrCore.java:1916)

我们在码头集群模式（5碎片）运行的Solr 4.7。
每个碎片不同的主机与一个动物园管理员服务器上运行。

We run Solr 4.7 in Cluster mode (5 shards) on jetty. Each shard run on a different host with one zookeeper server.

我检查了动物园管理员日志，我看不到任何东西在那里。

I checked the zookeeper log and I cannot see anything there.

唯一的区别是，在/ overseer_election /选举夹我看到这个特定服务器重复3次，而其他服务器仅提及两次。

The only difference is that in the /overseer_election/election folder I see this specific server repeated 3 times, while the other server are only mentioned twice.

  45654861x41276x432-x.x.x.x:7070_solr-n_00000003xx
  74030267x31685x368-x.x.x.x:7070_solr-n_00000003xx
  74030267x31685x369-x.x.x.x:7070_solr-n_00000003xx

甚至不知道这是否是相关的。 （是真的吗？）
任何线索，我们可以做些什么其他检查？

Not even sure if this is relevant. (Can it be?) Any clue what other check can we do?

推荐答案

我们想通了！
问题是，码头没有真正停止，所以我们有2个正在运行的进程，无论出于何种原因，这是很好的阅读，但不能写入。

We figured out! The issue was that jetty didn't really stop so we had 2 running processes, for whatever reason this was fine for reading but not for writing.

杀上了年纪的java程序解决了问题。

Killing the older java process solved the issue.

这篇关于Solr的问题：CLUSTERSTATE说，我们是领导者，但我们本地不这么认为的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！