lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mikhail Magdi Ibraheem (JIRA)" <j...@apache.org>
Subject [jira] [Created] (SOLR-11301) Delete collection time out after 180s or create the configset time out:300s
Date Thu, 31 Aug 2017 07:57:00 GMT
Mikhail Magdi Ibraheem created SOLR-11301:
---------------------------------------------

             Summary: Delete collection time out after 180s or  create the configset time
out:300s
                 Key: SOLR-11301
                 URL: https://issues.apache.org/jira/browse/SOLR-11301
             Project: Solr
          Issue Type: Bug
      Security Level: Public (Default Security Level. Issues are Public)
          Components: replication (java), SolrCloud
    Affects Versions: 6.6
            Reporter: Mikhail Magdi Ibraheem


I have 1 zookeeper node and one solr node. Sometimes when trying to create or delete collection
there is 
"SEVERE: null:org.apache.solr.common.SolrException: delete the collection time out:180s" 
Or "create the configset time out:300s.". This happens always until I restart solr. then after
some time, it happens again until restart. 

After checking the code I found that solr puts a task node to zookeeper /overseer/collection-queue-work/qnr-0000012764
/overseer/collection-queue-work/qn-0000012764 then a watcher listen for this and process the
task, then delete the response node which triggers the latchWatcher to notify the thread that
the task finished. The timeout for this is 180 seconds (hard coded). I think that sometimes
the watcher to trigger the processor not triggered? Is that a bug? How to fix that?
Please help.




--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message