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

Reply via email to