That could be. I had a flaky network and I had to rerun my script twice. Maybe
it got into some inconsistent state. I will keep an eye on this. If I am able
to reproduce, then I will create a JIRA.
Bosco
On 11/20/15, 10:34 AM, "Anshum Gupta" wrote:
>This uses the Collections API and should
This uses the Collections API and shouldn't have led to that state. Have
you had similar issues before?
I'm also wondering if you already had something from previous runs/installs
on the fs/zk.
On Fri, Nov 20, 2015 at 10:26 AM, Don Bosco Durai wrote:
> Anshum,
>
> Thanks for the workaround. It
Anshum,
Thanks for the workaround. It resolved my issue.
Here is the command I used. It is pretty standard and has worked for me almost
all the time (so far)...
bin/solr create -c my_collection -d /tmp/solr_configsets/my_collection/conf -s
3 -rf 1
Thanks
Bosco
On 11/20/15, 9:56 AM, "Ans
You can manually update the cluster state so that the range for shard1 says
8000-d554. Also remove the "parent" tag from there.
Can you tell me how did you create this collection ? This shouldn't really
happen unless you didn't use the Collections API to create the collection.
On Fri,
I am using Solr 5.2 version.
Thanks
Bosco
On 11/20/15, 9:39 AM, "Don Bosco Durai" wrote:
>I created a 3 shard cluster, but seems for one of the shard, the range is
>empty. Anyway to fix it without deleting and recreating the collection?
>
>2015-11-20 08:59:50,901 [solr,writer=0] ERROR
>a
I created a 3 shard cluster, but seems for one of the shard, the range is
empty. Anyway to fix it without deleting and recreating the collection?
2015-11-20 08:59:50,901 [solr,writer=0] ERROR
apache.solr.client.solrj.impl.CloudSolrClient (CloudSolrClient.java:902) -
Request to collection my_col
