You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Anshum Gupta (JIRA)" <ji...@apache.org> on 2014/08/11 17:08:12 UTC
[jira] [Resolved] (SOLR-6361) /admin/collection API reload action
is not work. --Got timeout exception
[ https://issues.apache.org/jira/browse/SOLR-6361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Anshum Gupta resolved SOLR-6361.
--------------------------------
Resolution: Invalid
That node is pretty much used for internal communication and not for external visibility. It's used for the marking and consuming of the response internally.
That 3 min TIMEOUT is the http timeout and even though the request said it timeout (the parent request did), the internal requests would most likely have gone through. That's the case with a lot of long running Collection API calls.
I'd recommend you ask such questions on the mailing list before creating a JIRA. I'm closing this one out for now.
P.S: For long running collection API calls, check out the ASYNC mode of the calls. At the same time, I'm not sure if ASYNC support for RELOAD exists at this time. If it doesn't feel free to create a JIRA for that one.
> /admin/collection API reload action is not work. --Got timeout exception
> ------------------------------------------------------------------------
>
> Key: SOLR-6361
> URL: https://issues.apache.org/jira/browse/SOLR-6361
> Project: Solr
> Issue Type: Bug
> Components: clients - java
> Affects Versions: 4.9
> Environment: Ubuntu 10.04+Jdk 1.7_55
> One Zookeeper + Two shards
> Reporter: Lewis Liu
> Priority: Critical
> Labels: /admin/collections?action=reload
> Original Estimate: 120h
> Remaining Estimate: 120h
>
> I just updated the schema.xml and uploaded into zookeeper, I want to make all shards effecitve immediately ,So i call the api /solr/admin/collections?action=reload&name=collection4, After 3 minutes i got
> exception like this:
> org.apache.solr.common.SolrException: reloadcollection the collection time out:180s
> at org.apache.solr.handler.admin.CollectionsHandler.handleResponse(CollectionsHandler.java:368)
> at org.apache.solr.handler.admin.CollectionsHandler.handleResponse(CollectionsHandler.java:320)
> at
> I checked the log ,Found these log
> [2014-08-11 17:19:55,227] [main-SendThread(localhost:2181)] DEBUG org.apache.zookeeper.ClientCnxn - Got WatchedEvent state:SyncConnected type:NodeDeleted path:/overseer/collection-queue-work/qnr-0000000068 for sessionid 0x147c387a9b3000b
> [2014-08-11 17:19:55,227] [main-EventThread] INFO org.apache.solr.cloud.DistributedQueue - LatchChildWatcher fired on path: /overseer/collection-queue-work/qnr-0000000068 state: SyncConnected type NodeDeleted
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org