Could you post your clusterstate.json? Or at least the "live nodes" section of your ZK config? (adminUI>>cloud>>tree>>live_nodes. The addresses of my nodes are things like 192.168.1.201:8983_solr. I'm wondering if you're taking your node names from the information ZK records or assuming it's 127.0.0.1....
On Sat, Jul 18, 2015 at 8:56 AM, Savvas Andreas Moysidis <savvas.andreas.moysi...@gmail.com> wrote: > Thanks Eric, > > The strange thing is that although I have set the log level to "ALL" I see > no error messages in the logs (apart from the line saying that the response > is a 400 one). > > I'm quite confident the configset does exist as the collection gets created > fine if I don't specify the createNodeSet param. > > Complete mystery..! I'll keep on troubleshooting and report back with my > findings. > > Cheers, > Savvas > > On 17 July 2015 at 02:14, Erick Erickson <erickerick...@gmail.com> wrote: > >> There were a couple of cases where the "no live servers" was being >> returned when the error was something completely different. Does the >> Solr log show something more useful? And are you sure you have a >> configset named collection_A? >> >> 'cause this works (admittedly on 5.x) fine for me, and I'm quite sure >> there are bunches of automated tests that would be failing so I >> suspect it's just a misleading error being returned. >> >> Best, >> Erick >> >> On Thu, Jul 16, 2015 at 2:22 AM, Savvas Andreas Moysidis >> <savvas.andreas.moysi...@gmail.com> wrote: >> > Hello There, >> > >> > I am trying to use the createNodeSet parameter when creating a new >> > collection but I'm getting an error when doing so. >> > >> > More specifically, I have four Solr instances running locally in separate >> > JVMs (127.0.0.1:8983, 127.0.0.1:8984, 127.0.0.1:8985, 127.0.0.1:8986) >> and a >> > standalone Zookeeper instance which all Solr instances point to. The four >> > Solr instances have no collections added to them and are all up and >> running >> > (I can access the admin page in all of them). >> > >> > Now, I want to create a collections in only two of these four instances ( >> > 127.0.0.1:8983, 127.0.0.1:8984) but when I hit one instance with the >> > following URL: >> > >> > >> http://localhost:8983/solr/admin/collections?action=CREATE&name=collection_A&numShards=1&replicationFactor=2&maxShardsPerNode=1&createNodeSet=127.0.0.1:8983_solr,127.0.0.1:8984_solr&collection.configName=collection_A >> > >> > I am getting the following response: >> > >> > <response> >> > <lst name="responseHeader"> >> > <int name="status">400</int> >> > <int name="QTime">3503</int> >> > </lst> >> > <str name="Operation createcollection caused exception:"> >> > >> org.apache.solr.common.SolrException:org.apache.solr.common.SolrException: >> > Cannot create collection collection_A. No live Solr-instances among >> > Solr-instances specified in createNodeSet:127.0.0.1:8983_solr, >> 127.0.0.1:8984 >> > _solr >> > </str> >> > <lst name="exception"> >> > <str name="msg"> >> > Cannot create collection collection_A. No live Solr-instances among >> > Solr-instances specified in createNodeSet:127.0.0.1:8983_solr, >> 127.0.0.1:8984 >> > _solr >> > </str> >> > <int name="rspCode">400</int> >> > </lst> >> > <lst name="error"> >> > <str name="msg"> >> > Cannot create collection collection_A. No live Solr-instances among >> > Solr-instances specified in createNodeSet:127.0.0.1:8983_solr, >> 127.0.0.1:8984 >> > _solr >> > </str> >> > <int name="code">400</int> >> > </lst> >> > </response> >> > >> > >> > The instances are definitely up and running (at least the admin console >> can >> > be accessed as mentioned) and if I remove the createNodeSet parameter the >> > collection is created as expected. >> > >> > Am I missing something obvious or is this a bug? >> > >> > The exact Solr version I'm using is 4.9.1. >> > >> > Any pointers would be much appreciated. >> > >> > Thanks, >> > Savvas >>
