Hi Edwin, Yes seems to work for me with this command if we use -s instead:
-solr.cmd start -p 8983 -s "C:\solrsc8_521_in\example\cloud\node1\solr" -z "localhost:2181,localhost:2182,localhost:2183" -noprompt I noticed you did not put a start in your command? Note the below command won't work with the -e parameter as this will runs the example action. The script will attempt to start two solr nodes on 8983 and 7574 and attach the nodes to zk with -z localhost:2181,localhost:2182,localhost:2183 without quotation marks. So the below line fails. -solr.cmd -e cloud -z "localhost:2181,localhost:2182,localh ost:2183" -noprompt (won't work with quotation marks) I can see the Cloud tab on the left side and I do not see any collections yet. I believe this is a good start since I have not added in any collections yet. Have you tried to add a collection to 1 shard and 3 replicas for example? Best regards, Adrian Liew | Consultant Application Developer Avanade Malaysia Sdn. Bhd..| Consulting Services (: Direct: +(603) 2382 5668 È: +6010-2288030 -----Original Message----- From: Zheng Lin Edwin Yeo [mailto:edwinye...@gmail.com] Sent: Tuesday, July 7, 2015 11:46 AM To: solr-user@lucene.apache.org Subject: Re: Migrating from Solr 5.1 to Solr 5.2.1 I tried to put the 3 ZooKeeper ports together with the double-quotes and it works. - bin\solr.cmd -p 8983 -s example\node1\solr -z "localhost:2181,localhost:2182,localhost:2183" Regards, Edwin On 7 July 2015 at 10:59, Zheng Lin Edwin Yeo <edwinye...@gmail.com> wrote: > Thank you Timothy. > > I've managed to start Solr 5.2.1 by using bin\solr.cmd. > > However, I could not get it to start it together with 3 instances of > external ZooKeeper with this command > - bin\solr.cmd -e cloud -z > localhost:2181,localhost:2182,localhost:2183 > > I'll get the error *"Invalid command-line option: localhost:2182"* if > I enter the above command. > > > I can only managed to start it if I define only 1 instance of the > ZooKeeper > Eg: - bin\solr.cmd -e cloud -z localhost:2181 > > > Regards, > Edwin > > > On 7 July 2015 at 00:07, Timothy Potter <thelabd...@gmail.com> wrote: > >> Hi Edwin, >> >> You'll need to use the bin\solr.cmd to start Solr as it now requires >> some additional system properties to be set. Put simply, starting >> solr using java -jar start.jar is not supported. Please try >> bin\solr.cmd and let us know if you run into any issues. You can set >> any additional system properties (-D) you need in the bin\solr.in.cmd >> script >> >> Cheers, >> Tim >> >> On Fri, Jul 3, 2015 at 2:07 AM, Zheng Lin Edwin Yeo >> <edwinye...@gmail.com> wrote: >> > Hi, >> > >> > I'm trying to migrate from Solr 5.1 to Solr 5.2.1. However, I faced >> > some problems when I'm trying to migrate my index over, and when >> > I'm trying >> to >> > link up the external ZooKeeper to Solr. >> > I'm using ZooKeeper 3.4.6 >> > >> > In Solr 5.1, I used this command to start Solr for both Shard1 and >> Shard2: >> > >> > java -D64 -Dsolr.clustering.enabled=true -Xms512M -Xmx4096M >> > -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/tmp/heapDumps >> > -DzkHost=localhost:2181,localhost:2182,localhost:2183 -jar >> > start.jar >> > >> > However, I get the following error in Solr 5.2.1: >> > *Error: Unable to access jarfile start.jar* >> > >> > For ZooKeeper, I've been using the zkCli.bat file under >> > server\scripts\cloud-scripts: >> > >> > zkcli.bat -zkhost localhost:2181 \ -cmd upconfig -confname >> > collection1 -confdir >> > >> C:\Users\edwin_000\Desktop\edwin\edm-5.2.1\configuration\collection1\ >> conf >> > >> > However, I get the following error in Solr 5.2.1 >> > *Error: Could not find or load main class >> > org.apache.solr.cloud.ZkCLI* >> > >> > Is there any changes to the code structure in Solr 5.2.1 as >> > compared to >> the >> > older versions? >> > >> > >> > Regards, >> > Edwin >> > >
