When you say you move to different machines, did you copy the zoo_data from
your old setup, or did you just start up zookeeper and your shards one by
one? Also did you use collection API to create the collection or just
start up your cores and let them attach to ZK. I believe the ZK rules for
ass
Try sending requests to your shards with &distrib=false. See if the
results agree with the SolrCloud graph or whether the docs you get
back are inconsistent with the shard labels in the admin page. The
&distrib=false bit keeps the query from going to other shards and
will tell you if the current st
Firstly, using 1 zookeeper machine is not at all ideal. See
http://wiki.apache.org/hadoop/ZooKeeper/FAQ#A7
I've never personally seen such an issue. Can you give screen shots of
the cloud graph on each node? Use an image hosting service because the
mailing list won't allow attachments.
On Tue, Ju
Thanks for the response.
I use 4.3 and have this issue.
-Original Message-
From: Upayavira [mailto:u...@odoko.co.uk]
Sent: Tuesday, June 18, 2013 12:57 PM
To: solr-user@lucene.apache.org
Subject: Re: Shard identification
What version of Solr? I had something like this on 4.2.1
What version of Solr? I had something like this on 4.2.1. Upgraging to
4.3 sorted it.
Upayavira
On Tue, Jun 18, 2013, at 09:37 AM, Ophir Michaeli wrote:
> Hi,
>
> I built a 2 shards and 2 replicas system that works ok on a local
> machine, 1
> zookeeper on shard 1.
> It appears ok on the solar
