Hello Renning. Sounds like https://issues.apache.org/jira/browse/SOLR-6246
A workaround that may not be very appealing is to create a new collection and to use aliases to point to it in you code/call Thanks. On 30 September 2015 at 01:44, r b <chopf...@gmail.com> wrote: > lately, my workflow has been 1) make some config changes, 2) upload to > zookeeper, 3) use collections API to reload config for the collection. > this has been working pretty well. > > starting last week, i started using the AnalyzingInfixLookupFactory in > a SuggestComponent (up until then, it was just the > FuzzyLookupFactory). the Infix lookup requires an indexPath where it > keeps an index on disk. > > first couple times i used this and went through my cycle, it was no > problem. but then i started getting some strange errors: > > LockObtainFailedException: Lock obtain timed out: > NativeFSLock@ > /opt/solr-5.2.1/server/solr/myCollection_shard4_replica6/data/myInfixLookup/write.lock > > now when i go and try to update the config and reload, i do not get a > response back and the connection drops after a minute. > > when i run other collections API commands, i notice them queueing up > in the overseer collection work queue. after a seemingly long while, > they disappear. i assumed it was just that some solrcloud nodes were > just taking a while, but when playing with the suggest component's > handler, i notice that not all of the nodes get the new config > changes. > > has anyone else seen this before? maybe there is somethign wrong with > my workflow that caused this? > > -renning > -- Arcadius Ahouansou Menelic Ltd | Information is Power M: 07908761999 W: www.menelic.com ---
