Alan, That was brilliant! My test harness was behind a couple of notches. Hah! So, now we open yet another can of strange looking creatures, namely:
No live SolrServers available to handle this request:[http://127.0.1.1:8983/solr/collection1] at org.apache.solr.client.solrj.impl.CloudSolrServer.directUpdate(CloudSolrServer.java:347) 3 times, once for each URL I passed into the server. Here is the code: String zkurl = "10.1.10.178:2181"; String solrurla = "10.1.10.178:8983"; String solrurlb = "10.1.10.178:7574"; String solrurlc = "10.1.10.178:7590"; LBHttpSolrServer sv = new LBHttpSolrServer(solrurla,solrurlb,solrurlc); CloudSolrServer server = new CloudSolrServer(zkurl,sv); server.setDefaultCollection("collection1"); I am struggling to imagine how 10.1.10.178 got translated to 127.0.1.1 and the port assignments ignored for each URL passed in. That error message seems well known to search engines. One suggestion is to check the zookeeper logs. According to the zookeeper's log4j properties, there should be a zookeeper.log in the zookeeper directory. There is no such log. I went to /etc/zookeeper/Version_2 and looked at log.1 (binary) but could see hints that this might be where the 127.0.1.1 is coming from: zookeeper sending such an error message back. This would suggest that, somehow or other, my nodes are not properly registering themselves, though no error messages were tossed when each node was booted. solr.log for node1 only reflects queries from the admin page. That's what I am working on now. Thanks! On Fri, Nov 1, 2013 at 6:03 AM, Alan Woodward <a...@flax.co.uk> wrote: > Unknown document router errors are usually caused by using different solr and > solrj versions - which version of solr and solrj are you using? > > Alan Woodward > www.flax.co.uk > > > On 1 Nov 2013, at 04:19, Jack Park wrote: > >> After digging deeper (slow for a *nix newbee), I uncovered issues with >> the java installation. A step in installation of Oracle Java has it >> that you -install "java" with the path to <dir>/bin/java. That done, >> zookeeper seems to be running. >> >> I booted three cores (on the same box) -- this is the simple one-box >> 3-node cloud test, and used the test code from the Lucidworks course >> to send over and read some documents. That failed with this: >> Unknown document router '{name=compositeId}' >> >> Lots more research. >> Closer... >> >> On Thu, Oct 31, 2013 at 5:44 PM, Jack Park <jackp...@topicquests.org> wrote: >>> Latest zookeeper is installed on an Ubuntu server box. >>> Java is 1.7 latest build. >>> whereis points to java just fine. >>> /etc/zookeeper is empty. >>> >>> boot zookeeper from /bin as sudo ./zkServer.sh start >>> Console says "Started" >>> /etc/zookeeper now has a .pid file >>> In another console, ./zkServer.sh status returns: >>> "It's probably not running" >>> >>> An interesting fact: the log4j.properties file says there should be a >>> zookeeper.log file in "."; there is no log file. When I do a text >>> search in the zookeeper source code for where it picks up the >>> log4j.properties, nothing is found. >>> >>> Fascinating, what? This must be a common beginner's question, not >>> well covered in web-search for my context. Does it ring any bells? >>> >>> Many thanks. >>> Jack >
