[collections] was empty until I used the correct zkcli script from the solr distribution.
I uploaded the config - java -classpath .:/production/v8p/deploy/svc.war/WEB-INF/lib/* org.apache.solr.cloud.ZkCLI -cmd upconfig -zkhost localhost:2181 -confdir /data/v8p/solr/root/conf -confname defaultconfig Then ran the bootstrap - java -classpath .:/production/v8p/deploy/svc.war/WEB-INF/lib/* org.apache.solr.cloud.ZkCLI -cmd bootstrap -zkhost 127.0.0.1:2181 -solrhome /data/v8p/solr If I'm not mistaken, I don't need to link anything if the collection names are defined in the core element [solr.xml] The cloud admin page shows each core now, but I'm curious how it know how many shards I want to use... I think I missed that somewhere. Jeremy D. Branham Performance Technologist II Sprint University Performance Support Fort Worth, TX | Tel: **DOTNET http://JeremyBranham.Wordpress.com http://www.linkedin.com/in/jeremybranham -----Original Message----- From: Erick Erickson [mailto:erickerick...@gmail.com] Sent: Tuesday, October 22, 2013 3:57 AM To: solr-user@lucene.apache.org Subject: Re: External Zookeeper and JBOSS What happens if you look in "collections"? Best, Erick On Mon, Oct 21, 2013 at 9:55 PM, Shawn Heisey <s...@elyograg.org> wrote: > On 10/21/2013 1:19 PM, Branham, Jeremy [HR] wrote: > >> Sorl.xml [simplified by removing additional cores] >> >> <?xml version="1.0" encoding="UTF-8" ?> <solr persistent="true" >> sharedLib="lib" zkHost="192.168.1.101:2181"> >> <cores adminPath="/admin/cores"> >> <core schema="/data/v8p/solr/root/**schema/schema.xml" >> instanceDir="/data/v8p/solr/**root/" name="wdsp" >> dataDir="/data/v8p/solr/wdsp2/**data"/> >> <core schema="/data/v8p/solr/root/**schema/schema.xml" >> instanceDir="/data/v8p/solr/**root/" name="wdsp2" >> dataDir="/data/v8p/solr/wdsp/**data"/> >> </cores> >> </solr> >> > > These cores that you have listed here do not look like > SolrCloud-related cores, because they do not reference a collection or > a shard. Here's what I've got on a 4.2.1 box where all cores were > automatically created by the CREATE action on the collections API: > > <core schema="schema.xml" loadOnStartup="true" shard="shard1" > instanceDir="eatatjoes_shard1_**replica2/" transient="false" > name="eatatjoes_shard1_**replica2" config="solrconfig.xml" > collection="eatatjoes"/> > <core schema="schema.xml" loadOnStartup="true" shard="shard1" > instanceDir="test3_shard1_**replica1/" transient="false" > name="test3_shard1_replica1" config="solrconfig.xml" collection="test3"/> > <core schema="schema.xml" loadOnStartup="true" shard="shard1" > instanceDir="smb2_shard1_**replica1/" transient="false" > name="smb2_shard1_replica1" config="solrconfig.xml" > collection="smb2"/> > > On the commandline script -- the zkCli.sh script comes with zookeeper, > but it is not aware of anything having to do with SolrCloud. There is > another script named zkcli.sh (note the lowercase C) that comes with > the solr example (in example/cloud-scripts)- it's a very different > script and will accept the options that you tried to give. > > I do wonder how much pain would be caused by renaming the Solr zkcli > script so it's not so similar to the one that comes with Zookeeper. > > Thanks, > Shawn > > ________________________________ This e-mail may contain Sprint proprietary information intended for the sole use of the recipient(s). Any use by others is prohibited. If you are not the intended recipient, please contact the sender and delete all copies of the message.
