Hi Mark,
Did you get a chance to look into the issues with running the embedded Zookeeper ensemble, as per Example C, from the http://wiki.apache.org/solr/SolrCloud2

Hi All,
Did anyone else run multiple shards with embedded zk ensemble successfully? If so would like some tips on any issues that you came across.

Regards,
Dipti

From: diptis <[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>>
Date: Fri, 23 Dec 2011 10:32:52 -0700
To: "[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>" <[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>>
Subject: Re: Release build or code for SolrCloud

Hi Mark,
There is some issue with specifying localhost vs actual host names for zk. When I changed my script to specify the actual hostname (which should be local by default) the first, 2nd and 3rd instances came up, that have the embedded zk running. Now, I am getting the same exception for the 4th AMI which in NOT part of the zookeeper ensemble. I want to zk only on 3 of the 4 instances.

java -Dbootstrap_confdir=./solr/conf –DzkRun="<ami-1>9983>"
-DzkHost=<ami-1>:9983,<ami-2>:9983,<ami-3>:9983 -DnumShards=2 -jar
start.jar

Dipti

From: Mark Miller <[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>>
Reply-To: "[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>" <[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>>
Date: Fri, 23 Dec 2011 09:34:52 -0700
To: diptis <[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>>
Subject: Re: Release build or code for SolrCloud

I'm having trouble getting a quorum up using the built in SolrZkServer as well - so i have not been able to replicate this - I'll have to keep digging. Not sure if it's due to a ZooKeeper update or what yet.

2011/12/21 Dipti Srivastava <[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>>
Hi Mark,
Thanks! So now I am deploying a 4 node cluster on AMI's and the main
instance that bootstraps the config to the zookeeper does not come up I
get an exception as follows. My solrcloud.sh looks like

#!/usr/bin/env bash

cd ..

rm -r -f example/solr/zoo_data
rm -f example/example.log

cd example
#java -DzkRun -DnumShards=2 -DSTOP.PORT=7983 -DSTOP.KEY=key -jar start.jar
1>example.log 2>&1 &
java -Dbootstrap_confdir=./solr/conf -DzkRun
-DzkHost=<ami-1>:9983,<ami-2>:9983,<ami-3>:9983 -DnumShards=2 -jar
start.jar
And when I RUN it----

--CLOUD--[ec2-user@ cloud-dev]$ ./solrcloud.sh
2011-12-22 02:18:23.352:INFO::Logging to STDERR via
org.mortbay.log.StdErrLog
2011-12-22 02:18:23.510:INFO::jetty-6.1-SNAPSHOT
Dec 22, 2011 2:18:23 AM org.apache.solr.core.SolrResourceLoader
locateSolrHome
INFO: JNDI not configured for solr (NoInitialContextEx)
Dec 22, 2011 2:18:23 AM org.apache.solr.core.SolrResourceLoader
locateSolrHome
INFO: solr home defaulted to 'solr/' (could not find system property or
JNDI)
Dec 22, 2011 2:18:23 AM org.apache.solr.core.SolrResourceLoader <init>
INFO: Solr home set to 'solr/'
Dec 22, 2011 2:18:23 AM org.apache.solr.servlet.SolrDispatchFilter init
INFO: SolrDispatchFilter.init()
Dec 22, 2011 2:18:23 AM org.apache.solr.core.SolrResourceLoader
locateSolrHome
INFO: JNDI not configured for solr (NoInitialContextEx)
Dec 22, 2011 2:18:23 AM org.apache.solr.core.SolrResourceLoader
locateSolrHome
INFO: solr home defaulted to 'solr/' (could not find system property or
JNDI)
Dec 22, 2011 2:18:23 AM org.apache.solr.core.CoreContainer$Initializer
initialize
INFO: looking for solr.xml: /home/ec2-user/solrcloud/example/solr/solr.xml
Dec 22, 2011 2:18:23 AM org.apache.solr.core.CoreContainer <init>
INFO: New CoreContainer 1406140084
Dec 22, 2011 2:18:23 AM org.apache.solr.core.SolrResourceLoader
locateSolrHome
INFO: JNDI not configured for solr (NoInitialContextEx)
Dec 22, 2011 2:18:23 AM org.apache.solr.core.SolrResourceLoader
locateSolrHome
INFO: solr home defaulted to 'solr/' (could not find system property or
JNDI)
Dec 22, 2011 2:18:23 AM org.apache.solr.core.SolrResourceLoader <init>
INFO: Solr home set to 'solr/'
Dec 22, 2011 2:18:24 AM org.apache.solr.cloud.SolrZkServerProps
getProperties
INFO: Reading configuration from: solr/zoo.cfg
Dec 22, 2011 2:18:24 AM org.apache.solr.cloud.SolrZkServerProps
parseProperties
INFO: Defaulting to majority quorums
Dec 22, 2011 2:18:24 AM org.apache.solr.servlet.SolrDispatchFilter init
SEVERE: Could not start Solr. Check solr/home property and the logs
java.lang.IllegalArgumentException: port out of range:-1
       at java.net.InetSocketAddress.<init>(InetSocketAddress.java:83)
       at java.net.InetSocketAddress.<init>(InetSocketAddress.java:63)
       at
org.apache.solr.cloud.SolrZkServerProps.setClientPort(SolrZkServer.java:310
)
       at
org.apache.solr.cloud.SolrZkServerProps.getMySeverId(SolrZkServer.java:273)
       at
org.apache.solr.cloud.SolrZkServerProps.parseProperties(SolrZkServer.java:4
50)
       at org.apache.solr.cloud.SolrZkServer.parseConfig(SolrZkServer.java:85)
       at
org.apache.solr.core.CoreContainer.initZooKeeper(CoreContainer.java:147)
       at org.apache.solr.core.CoreContainer.load(CoreContainer.java:329)
       at org.apache.solr.core.CoreContainer.load(CoreContainer.java:282)
       at
org.apache.solr.core.CoreContainer$Initializer.initialize(CoreContainer.jav
a:231)
       at
org.apache.solr.servlet.SolrDispatchFilter.init(SolrDispatchFilter.java:93)
       at org.mortbay.jetty.servlet.FilterHolder.doStart(FilterHolder.java:97)
       at
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
       at
org.mortbay.jetty.servlet.ServletHandler.initialize(ServletHandler.java:713
)
       at org.mortbay.jetty.servlet.Context.startContext(Context.java:140)
       at
org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1282
)
       at
org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:518)
       at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:499)
       at
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
       at
org.m

Hey Dipti -

Can you give the exact startup cmds you are using for each of the instances? I have got Example C going, so I'll have to try and dig into whatever you are seeing.

- mark

On Jan 27, 2012, at 12:53 PM, Dipti Srivastava wrote:

> Hi Mark,
> Did you get a chance to look into the issues with running the embedded Zookeeper ensemble, as per Example C, from the http://wiki.apache.org/solr/SolrCloud2
>
> Hi All,
> Did anyone else run multiple shards with embedded zk ensemble successfully? If so would like some tips on any issues that you came across.
>
> Regards,
> Dipti
>
> From: diptis <[EMAIL PROTECTED]>
> Date: Fri, 23 Dec 2011 10:32:52 -0700
> To: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
> Subject: Re: Release build or code for SolrCloud
>
> Hi Mark,
> There is some issue with specifying localhost vs actual host names for zk. When I changed my script to specify the actual hostname (which should be local by default) the first, 2nd and 3rd instances came up, that have the embedded zk running. Now, I am getting the same exception for the 4th AMI which in NOT part of the zookeeper ensemble. I want to zk only on 3 of the 4 instances.
>
> java -Dbootstrap_confdir=./solr/conf –DzkRun="<ami-1>9983>"
> -DzkHost=<ami-1>:9983,<ami-2>:9983,<ami-3>:9983 -DnumShards=2 -jar
> start.jar
>
> Dipti
>
> From: Mark Miller <[EMAIL PROTECTED]>
> Reply-To: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
> Date: Fri, 23 Dec 2011 09:34:52 -0700
> To: diptis <[EMAIL PROTECTED]>
> Subject: Re: Release build or code for SolrCloud
>
> I'm having trouble getting a quorum up using the built in SolrZkServer as well - so i have not been able to replicate this - I'll have to keep digging. Not sure if it's due to a ZooKeeper update or what yet.
>
> 2011/12/21 Dipti Srivastava <[EMAIL PROTECTED]>
>> Hi Mark,
>> Thanks! So now I am deploying a 4 node cluster on AMI's and the main
>> instance that bootstraps the config to the zookeeper does not come up I
>> get an exception as follows. My solrcloud.sh looks like
>>
>> #!/usr/bin/env bash
>>
>> cd ..
>>
>> rm -r -f example/solr/zoo_data
>> rm -f example/example.log
>>
>> cd example
>> #java -DzkRun -DnumShards=2 -DSTOP.PORT=7983 -DSTOP.KEY=key -jar start.jar
>> 1>example.log 2>&1 &
>> java -Dbootstrap_confdir=./solr/conf -DzkRun
>> -DzkHost=<ami-1>:9983,<ami-2>:9983,<ami-3>:9983 -DnumShards=2 -jar
>> start.jar
>>
>>
>>
>>
>> And when I RUN it----
>>
>> --CLOUD--[ec2-user@ cloud-dev]$ ./solrcloud.sh
>> 2011-12-22 02:18:23.352:INFO::Logging to STDERR via
>> org.mortbay.log.StdErrLog
>> 2011-12-22 02:18:23.510:INFO::jetty-6.1-SNAPSHOT
>> Dec 22, 2011 2:18:23 AM org.apache.solr.core.SolrResourceLoader
>> locateSolrHome
>> INFO: JNDI not configured for solr (NoInitialContextEx)
>> Dec 22, 2011 2:18:23 AM org.apache.solr.core.SolrResourceLoader
>> locateSolrHome
>> INFO: solr home defaulted to 'solr/' (could not find system property or
>> JNDI)
>> Dec 22, 2011 2:18:23 AM org.apache.solr.core.SolrResourceLoader <init>
>> INFO: Solr home set to 'solr/'
>> Dec 22, 2011 2:18:23 AM org.apache.solr.servlet.SolrDispatchFilter init
>> INFO: SolrDispatchFilter.init()
>> Dec 22, 2011 2:18:23 AM org.apache.solr.core.SolrResourceLoader
>> locateSolrHome
>> INFO: JNDI not configured for solr (NoInitialContextEx)
>> Dec 22, 2011 2:18:23 AM org.apache.solr.core.SolrResourceLoader
>> locateSolrHome
>> INFO: solr home defaulted to 'solr/' (could not find system property or
>> JNDI)
>> Dec 22, 2011 2:18:23 AM org.apache.solr.core.CoreContainer$Initializer
>> initialize
>> INFO: looking for solr.xml: /home/ec2-user/solrcloud/example/solr/solr.xml
>> Dec 22, 2011 2:18:23 AM org.apache.solr.core.CoreContainer <init>
>> INFO: New CoreContainer 1406140084
>> Dec 22, 2011 2:18:23 AM org.apache.solr.core.SolrResourceLoader
>> locateSolrHome
>> INFO: JNDI not configured for solr (NoInitialContextEx)
>> Dec 22, 2011 2:18:23 AM org.apache.solr.core.SolrResourceLoader
>> locateSolrHome

- Mark Miller
lucidimagination.com

Hi Mark,
I am trying to set up on 4 ami's, where 3 of the instances will have the
embedded ZK running. Here are the startup commands for all 4.

- Note that on the 4th instance I do not have the ZK host and bootstrap
conf dir specified. The 4th instance throws exception (earlier in this
email chain) at startup.
- Ideally, I should not have to specify the host for the -DzkRun since it
is the localhost, but without that I get the exception as well.

1. java -DzkRun=ec2-compute-1.amazonaws.com:9983
-Dsolr.solr.home=/home/ec2-user/solrcloud/example/solr
-Dbootstrap_confdir=/home/ec2-user/solrcloud//example/solr/conf
-DzkHost=ec2-compute-1.amazonaws.com:9983,ec2-compute-2.amazonaws.com:9983,
ec2-compute-3.amazonaws.com:9983 -DnumShards=2 -jar start.jar
2. java -DzkRun=ec2-compute-2.amazonaws.com:9983
-Dsolr.solr.home=/home/ec2-user/solrcloud/example/solr
-Dbootstrap_confdir=/home/ec2-user/solrcloud//example/solr/conf
-DzkHost=ec2-compute-1.amazonaws.com:9983,ec2-compute-2.amazonaws.com:9983,
ec2-compute-3.amazonaws.com:9983 -DnumShards=2 -jar start.jar
3. java -DzkRun=ec2-compute-3.amazonaws.com:9983
-Dsolr.solr.home=/home/ec2-user/solrcloud/example/solr
-Dbootstrap_confdir=/home/ec2-user/solrcloud//example/solr/conf
-DzkHost=ec2-compute-1.amazonaws.com:9983,ec2-compute-2.amazonaws.com:9983,
ec2-compute-3.amazonaws.com:9983 -DnumShards=2 -jar start.jar
4. java -Dsolr.solr.home=/home/ec2-user/solrcloud/example/solr
-DzkHost=ec2-compute-1.amazonaws.com:9983,ec2-compute-2.amazonaws.com:9983,
ec2-compute-3.amazonaws.com:9983 -DnumShards=2 -jar start.jar
Thanks,
Dipti

On 1/31/12 10:18 AM, "Mark Miller" <[EMAIL PROTECTED]> wrote:

>Hey Dipti -
>
>Can you give the exact startup cmds you are using for each of the
>instances? I have got Example C going, so I'll have to try and dig into
>whatever you are seeing.
>
>- mark
>
>On Jan 27, 2012, at 12:53 PM, Dipti Srivastava wrote:
>
>> Hi Mark,
>> Did you get a chance to look into the issues with running the embedded
>>Zookeeper ensemble, as per Example C, from the
>>http://wiki.apache.org/solr/SolrCloud2
>>
>> Hi All,
>> Did anyone else run multiple shards with embedded zk ensemble
>>successfully? If so would like some tips on any issues that you came
>>across.
>>
>> Regards,
>> Dipti
>>
>> From: diptis <[EMAIL PROTECTED]>
>> Date: Fri, 23 Dec 2011 10:32:52 -0700
>> To: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
>> Subject: Re: Release build or code for SolrCloud
>>
>> Hi Mark,
>> There is some issue with specifying localhost vs actual host names for
>>zk. When I changed my script to specify the actual hostname (which
>>should be local by default) the first, 2nd and 3rd instances came up,
>>that have the embedded zk running. Now, I am getting the same exception
>>for the 4th AMI which in NOT part of the zookeeper ensemble. I want to
>>zk only on 3 of the 4 instances.
>>
>> java -Dbootstrap_confdir=./solr/conf ­DzkRun="<ami-1>9983>"
>> -DzkHost=<ami-1>:9983,<ami-2>:9983,<ami-3>:9983 -DnumShards=2 -jar
>> start.jar
>>
>> Dipti
>>
>> From: Mark Miller <[EMAIL PROTECTED]>
>> Reply-To: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
>> Date: Fri, 23 Dec 2011 09:34:52 -0700
>> To: diptis <[EMAIL PROTECTED]>
>> Subject: Re: Release build or code for SolrCloud
>>
>> I'm having trouble getting a quorum up using the built in SolrZkServer
>>as well - so i have not been able to replicate this - I'll have to keep
>>digging. Not sure if it's due to a ZooKeeper update or what yet.
>>
>> 2011/12/21 Dipti Srivastava <[EMAIL PROTECTED]>
>>> Hi Mark,
>>> Thanks! So now I am deploying a 4 node cluster on AMI's and the main
>>> instance that bootstraps the config to the zookeeper does not come up I
>>> get an exception as follows. My solrcloud.sh looks like
>>>
>>> #!/usr/bin/env bash
>>>
>>> cd ..
>>>
>>> rm -r -f example/solr/zoo_data
>>> rm -f example/example.log
>>>
>>> cd example
>>> #java -DzkRun -DnumShards=2 -DSTOP.PORT=7983 -DSTOP.KEY=key -jar
>

This message is private and confidential. If you have received it in error, please notify the sender and remove it from your system.

Thanks Dipti!

One thing that seems off is that you are passing the bootstrap_confdir param on each instance?

Other than that though, the problem you are seeing is indeed a bug - though hidden if using localhost. I'll fix it here: https://issues.apache.org/jira/browse/SOLR-3091

Again, thanks for the detailed report.

- mark
On Feb 2, 2012, at 4:44 PM, Dipti Srivastava wrote:

> Hi Mark,
> I am trying to set up on 4 ami's, where 3 of the instances will have the
> embedded ZK running. Here are the startup commands for all 4.
>
> - Note that on the 4th instance I do not have the ZK host and bootstrap
> conf dir specified. The 4th instance throws exception (earlier in this
> email chain) at startup.
> - Ideally, I should not have to specify the host for the -DzkRun since it
> is the localhost, but without that I get the exception as well.
>
> 1. java -DzkRun=ec2-compute-1.amazonaws.com:9983
> -Dsolr.solr.home=/home/ec2-user/solrcloud/example/solr
> -Dbootstrap_confdir=/home/ec2-user/solrcloud//example/solr/conf
> -DzkHost=ec2-compute-1.amazonaws.com:9983,ec2-compute-2.amazonaws.com:9983,
> ec2-compute-3.amazonaws.com:9983 -DnumShards=2 -jar start.jar
>
>
> 2. java -DzkRun=ec2-compute-2.amazonaws.com:9983
> -Dsolr.solr.home=/home/ec2-user/solrcloud/example/solr
> -Dbootstrap_confdir=/home/ec2-user/solrcloud//example/solr/conf
> -DzkHost=ec2-compute-1.amazonaws.com:9983,ec2-compute-2.amazonaws.com:9983,
> ec2-compute-3.amazonaws.com:9983 -DnumShards=2 -jar start.jar
>
>
> 3. java -DzkRun=ec2-compute-3.amazonaws.com:9983
> -Dsolr.solr.home=/home/ec2-user/solrcloud/example/solr
> -Dbootstrap_confdir=/home/ec2-user/solrcloud//example/solr/conf
> -DzkHost=ec2-compute-1.amazonaws.com:9983,ec2-compute-2.amazonaws.com:9983,
> ec2-compute-3.amazonaws.com:9983 -DnumShards=2 -jar start.jar
>
>
> 4. java -Dsolr.solr.home=/home/ec2-user/solrcloud/example/solr
> -DzkHost=ec2-compute-1.amazonaws.com:9983,ec2-compute-2.amazonaws.com:9983,
> ec2-compute-3.amazonaws.com:9983 -DnumShards=2 -jar start.jar
>
>
> Thanks,
> Dipti
>
> On 1/31/12 10:18 AM, "Mark Miller" <[EMAIL PROTECTED]> wrote:
>
>> Hey Dipti -
>>
>> Can you give the exact startup cmds you are using for each of the
>> instances? I have got Example C going, so I'll have to try and dig into
>> whatever you are seeing.
>>
>> - mark
>>
>> On Jan 27, 2012, at 12:53 PM, Dipti Srivastava wrote:
>>
>>> Hi Mark,
>>> Did you get a chance to look into the issues with running the embedded
>>> Zookeeper ensemble, as per Example C, from the
>>> http://wiki.apache.org/solr/SolrCloud2
>>>
>>> Hi All,
>>> Did anyone else run multiple shards with embedded zk ensemble
>>> successfully? If so would like some tips on any issues that you came
>>> across.
>>>
>>> Regards,
>>> Dipti
>>>
>>> From: diptis <[EMAIL PROTECTED]>
>>> Date: Fri, 23 Dec 2011 10:32:52 -0700
>>> To: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
>>> Subject: Re: Release build or code for SolrCloud
>>>
>>> Hi Mark,
>>> There is some issue with specifying localhost vs actual host names for
>>> zk. When I changed my script to specify the actual hostname (which
>>> should be local by default) the first, 2nd and 3rd instances came up,
>>> that have the embedded zk running. Now, I am getting the same exception
>>> for the 4th AMI which in NOT part of the zookeeper ensemble. I want to
>>> zk only on 3 of the 4 instances.
>>>
>>> java -Dbootstrap_confdir=./solr/conf ­DzkRun="<ami-1>9983>"
>>> -DzkHost=<ami-1>:9983,<ami-2>:9983,<ami-3>:9983 -DnumShards=2 -jar
>>> start.jar
>>>
>>> Dipti
>>>
>>> From: Mark Miller <[EMAIL PROTECTED]>
>>> Reply-To: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
>>> Date: Fri, 23 Dec 2011 09:34:52 -0700
>>> To: diptis <[EMAIL PROTECTED]>
>>> Subject: Re: Release build or code for SolrCloud
>>>
>>> I'm having trouble getting a quorum up using the built in SolrZkServer
>>> as well - so i have not been able to replicate this - I'll have to keep
>>> digging. Not sure if it's due to a ZooKeeper update or what yet.

- Mark Miller
lucidimagination.com

Hi Mark,
Thanks for looking into the issue.

As for specifying the bootstrap dir for each instance with ZK, it was just
a typo on my side. I went back and looked at my script on the second and
3rd nodes and it did not have the bootstrp dir, so I had specified it for
only the very FIRST node that registers ZK.

2. java -DzkRun=ec2-compute-2.amazonaws.com:9983
-Dsolr.solr.home=/home/ec2-user/solrcloud/example/solr
-DzkHost=ec2-compute-1.amazonaws.com:9983,ec2-compute-2.amazonaws.com:9983,
ec2-compute-3.amazonaws.com:9983 -DnumShards=2 -jar start.jar
Thanks!
Dipti

On 2/2/12 8:27 PM, "Mark Miller" <[EMAIL PROTECTED]> wrote:

>Thanks Dipti!
>
>One thing that seems off is that you are passing the bootstrap_confdir
>param on each instance?
>
>Other than that though, the problem you are seeing is indeed a bug -
>though hidden if using localhost. I'll fix it here:
>https://issues.apache.org/jira/browse/SOLR-3091
>
>Again, thanks for the detailed report.
>
>- mark
>
>
>On Feb 2, 2012, at 4:44 PM, Dipti Srivastava wrote:
>
>> Hi Mark,
>> I am trying to set up on 4 ami's, where 3 of the instances will have the
>> embedded ZK running. Here are the startup commands for all 4.
>>
>> - Note that on the 4th instance I do not have the ZK host and bootstrap
>> conf dir specified. The 4th instance throws exception (earlier in this
>> email chain) at startup.
>> - Ideally, I should not have to specify the host for the -DzkRun since
>>it
>> is the localhost, but without that I get the exception as well.
>>
>> 1. java -DzkRun=ec2-compute-1.amazonaws.com:9983
>> -Dsolr.solr.home=/home/ec2-user/solrcloud/example/solr
>> -Dbootstrap_confdir=/home/ec2-user/solrcloud//example/solr/conf
>>
>>-DzkHost=ec2-compute-1.amazonaws.com:9983,ec2-compute-2.amazonaws.com:998
>>3,
>> ec2-compute-3.amazonaws.com:9983 -DnumShards=2 -jar start.jar
>>
>>
>> 2. java -DzkRun=ec2-compute-2.amazonaws.com:9983
>> -Dsolr.solr.home=/home/ec2-user/solrcloud/example/solr
>> -Dbootstrap_confdir=/home/ec2-user/solrcloud//example/solr/conf
>>
>>-DzkHost=ec2-compute-1.amazonaws.com:9983,ec2-compute-2.amazonaws.com:998
>>3,
>> ec2-compute-3.amazonaws.com:9983 -DnumShards=2 -jar start.jar
>>
>>
>> 3. java -DzkRun=ec2-compute-3.amazonaws.com:9983
>> -Dsolr.solr.home=/home/ec2-user/solrcloud/example/solr
>> -Dbootstrap_confdir=/home/ec2-user/solrcloud//example/solr/conf
>>
>>-DzkHost=ec2-compute-1.amazonaws.com:9983,ec2-compute-2.amazonaws.com:998
>>3,
>> ec2-compute-3.amazonaws.com:9983 -DnumShards=2 -jar start.jar
>>
>>
>> 4. java -Dsolr.solr.home=/home/ec2-user/solrcloud/example/solr
>>
>>-DzkHost=ec2-compute-1.amazonaws.com:9983,ec2-compute-2.amazonaws.com:998
>>3,
>> ec2-compute-3.amazonaws.com:9983 -DnumShards=2 -jar start.jar
>>
>>
>> Thanks,
>> Dipti
>>
>> On 1/31/12 10:18 AM, "Mark Miller" <[EMAIL PROTECTED]> wrote:
>>
>>> Hey Dipti -
>>>
>>> Can you give the exact startup cmds you are using for each of the
>>> instances? I have got Example C going, so I'll have to try and dig into
>>> whatever you are seeing.
>>>
>>> - mark
>>>
>>> On Jan 27, 2012, at 12:53 PM, Dipti Srivastava wrote:
>>>
>>>> Hi Mark,
>>>> Did you get a chance to look into the issues with running the embedded
>>>> Zookeeper ensemble, as per Example C, from the
>>>> http://wiki.apache.org/solr/SolrCloud2
>>>>
>>>> Hi All,
>>>> Did anyone else run multiple shards with embedded zk ensemble
>>>> successfully? If so would like some tips on any issues that you came
>>>> across.
>>>>
>>>> Regards,
>>>> Dipti
>>>>
>>>> From: diptis <[EMAIL PROTECTED]>
>>>> Date: Fri, 23 Dec 2011 10:32:52 -0700
>>>> To: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
>>>> Subject: Re: Release build or code for SolrCloud
>>>>
>>>> Hi Mark,
>>>> There is some issue with specifying localhost vs actual host names for
>>>> zk. When I changed my script to specify the actual hostname (which
>>>> should be local by default) the first, 2nd and 3rd instances came up,
>>>> that have the embedded zk running. Now, I am getting the same
This message is private and confidential. If you have received it in error, please notify the sender and remove it from your system.

i have the same problem, it seems that there is a bug in SolrZkServer class
(parseProperties method), that doesn't work well when you have an external
zookeeper ensemble.

Thanks,
 arin

--
View this message in context: http://lucene.472066.n3.nabble.com/SolrCloud-issues-running-with-embedded-zookeeper-ensemble-tp3694004p3751629.html
Sent from the Solr - User mailing list archive at Nabble.com.

On Feb 16, 2012, at 2:53 PM, arin g wrote:

> i have the same problem, it seems that there is a bug in SolrZkServer class
> (parseProperties method), that doesn't work well when you have an external
> zookeeper ensemble.
>

This issue was around using an embedded ensemble - an external ensemble makes SolrZkServer irrelevant.

What issue are you having? I just tried a basic test against an external ensemble.

What version are you using?

> Thanks,
> arin
>
> --
> View this message in context: http://lucene.472066.n3.nabble.com/SolrCloud-issues-running-with-embedded-zookeeper-ensemble-tp3694004p3751629.html
> Sent from the Solr - User mailing list archive at Nabble.com.

- Mark Miller
lucidimagination.com