What do you mean "indexed for the next shard"? With embeddedSolrServer,
you will have to map the documents into the proper shard (probably a
separate directory?), then keep very careful track of what shards they are,
then move them correctly to the proper "real" Solr server and... Simply indexing
a
Hi Erick,
Thanks for your response, well I got it resolved. I think the index were
not properly distributed and moreover I had some uneven behavior while
indexing, so to elaborate it,
I had three shards in my collection, I started indexing with
EmbeddedSolrServer and indexed around 50 Million Doc
It seems like for some reason you have shards that are not reachable.
What does your cloud stat in the admin UI tell you when you don't get
all the docs back?
Best,
Erick
On Fri, Jun 13, 2014 at 1:37 AM, Vineet Mishra wrote:
> Hi All,
>
> I am having a Cloud setup with 3 Shards and 2 Replica run
Are all the replicas up ?
Did you check if there is enough space on the disk?
How are you running the queries?
-
Thanks,
Michael
--
View this message in context:
http://lucene.472066.n3.nabble.com/Inconsistent-Behavior-of-Solr-Cloud-tp4141593p4141605.html
Sent from the Solr - User mailing
Hi All,
I am having a Cloud setup with 3 Shards and 2 Replica running on 3 Tomcats
with 3 External Zookeeper, all running on single machine.
I have Indexed around 70 Mln Documents that seems to be querying back fine.
When I index another 30 Mln to same, the result are vague as with the query
*:* i
