Erick Thanks for your response.
Logs don't seem to show any explicit errors (I have log level at INFO). I am attaching the logs from a 4.7 start and a 5.1 start here. Note that both logs seem to show the shards as "Down" initially but for 5.1, the state change to Active later on. Also, note that all the config files, libraries, jarfiles etc are the same for both Solr instances. Regards On Tue, May 19, 2015 at 11:57 AM, Erick Erickson <erickerick...@gmail.com> wrote: > What you've done _looks_ correct at a glance. Take a look at the Solr > logs. Don't bother trying to index things unless and until your nodes > are "active", it won't happen. > > My first guess is that you have some error in your schema or > solrconfig.xml files, syntax errors, typos, class names that are > mis-typed, jars that are missing, whatever. > > If that's true, the Solr log (or the screen if you're just running > from the command line) will show big ugly stack traces. > > If nothing shows up in the logs then I'm puzzled, but what you > describe is consistent with what I've seen in terms of having bad > configs and trying to create a collection. > > Best, > Erick > > On Tue, May 19, 2015 at 4:33 AM, Chetan Vora <chetanv...@gmail.com> wrote: > > Hi all > > > > We have a cluster of standalone Solr cores (Solr 4.3) for which we had > > built some custom plugins. I'm now trying to prototype converting the > > cluster to a Solr Cloud cluster. This is how I am trying to deploy the > > cores (in 4.7.2). > > > > 1. > > > > Start solr with zookeeper embedded. > > > > java -DzkRun -Djetty.port=8985 -jar start.jar > > 2. > > > > upload a config into Zookeeper (same config as the standalone cores) > > > > zkcli.bat -zkhost localhost:9985 -cmd upconfig -confdir myconfig > > -confname myconfig > > 3. > > > > Create a new collection (mycollection) of 2 shards using the > Collections > > API > > > http://localhost:8985/solr/admin/collections?action=CREATE&name=mycollection&numShards=2&replicationFactor=1&maxShardsPerNode=2&collection.configName=myconfig > > > > So at this point I have two shards under my solr directory with the > > appropriate core.properties > > > > But when I go to http://localhost:8985/solr/#/~cloud, I see that the two > > shards' status is "Down" when they are supposed to be active by default. > > > > And when I try to index documents in them using SolrJ (via > CloudSolrServer > > API) , I get the error "No live SolrServers available to handle this > > request". I restarted Solr but same issue. > > > > private CloudSolrServer cloudSolr; > > cloudSolr = new CloudSolrServer(zkHOST); > > cloudSolr.setZkClientTimeout(zkClientTimeout); > > cloudSolr.setDefaultCollection(collectionName); > > cloudSolr.connect(); > > cloudSolr.add(doc) > > > > What am I doing wrong? I did a lot of digging around and saw an old Jira > > bug saying that Solr Cloud shards won't be active until there are some > > documents in the index. If that is the reason, that's kind of like a > > catch-22 isn't it? > > > > So anyways, I also tried adding some test documents manually and > committed > > to see if things improved. Now on the shard statistics page, it correctly > > gives me the Numdocs count but when I try to query it says "no servers > > hosting shard". I next tried passing in shards.tolerant=true as a query > > parameter and search, but no cigar. It says 0 documents found. > > > > Any help would be appreciated. My main objective is to rebuilt the old > > standalone cores using SolrCloud and test to see if our custom > > requesthandlers still work as expected. And at this point, I can't index > > documents inside of the 4.7 Solr Cloud collection I have created. I am > > trying to use a 4.x SolrCloud release as it seems the internal APIs have > > changed quite a bit for the 5.x releases and our custom requesthandlers > > don't work anymore as expected. > > > > Thanks and Regards >
