lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Maxim Novikov (JIRA)" <>
Subject [jira] [Created] (SOLR-5961) Solr gets crazy on /overseer/queue state change
Date Fri, 04 Apr 2014 20:45:15 GMT
Maxim Novikov created SOLR-5961:

             Summary: Solr gets crazy on /overseer/queue state change
                 Key: SOLR-5961
             Project: Solr
          Issue Type: Bug
          Components: SolrCloud
    Affects Versions: 4.7.1
         Environment: CentOS, 1 shard - 3 replicas, ZK cluster with 3 nodes (separate machines)
            Reporter: Maxim Novikov
            Priority: Critical

No idea how to reproduce it, but sometimes Solr stars littering the log with the following

419158 [localhost-startStop-1-EventThread] INFO  ?
LatchChildWatcher fired on path: /overseer/queue state: SyncConnected type NodeChildrenChanged

419190 [Thread-3] INFO  ? Update state numShards=1 message={

It continues spamming these messages with no delay and the restarting of all the nodes does
not help. I have even tried to stop all the nodes in the cluster first, but then when I start
one, the behavior doesn't change, it gets crazy nuts with this " /overseer/queue state" again.

PS The only way to handle this was to stop everything, manually clean up all the data in ZooKeeper
related to Solr, and then rebuild everything from scratch. As you should understand, it is
kinda unbearable in the production environment.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message