Hash ranges should have been assigned automatically when you
created the collection unless you created the collection with the implicit
router. What was the command you used to create the collection?
Best,
Erick
On Thu, Feb 4, 2016 at 1:21 PM, Aki Balogh <a...@marketmuse.com> wrote:
> I'm not sure how these hash ranges were determined, so I'm not sure if I
> should be manually setting them or somehow allowing solr to pick them for
> this shard.
>
> Thanks,
> Aki
>
>
>
> On Thu, Feb 4, 2016 at 4:12 PM, Aki Balogh <a...@marketmuse.com> wrote:
>
>> Shawn,
>>
>> Thanks - this is very helpful.
>>
>> I found the state.json file and it indeed shows that the range for shard1
>> is null.
>>
>> In order to fix, do I need to upload a corrected state.json file with
>> corrected hash ranges? How can I do that? (zkcli.sh?)
>>
>> Thanks,
>> Aki
>>
>>
>> On Thu, Feb 4, 2016 at 4:10 PM, Shawn Heisey <apa...@elyograg.org> wrote:
>>
>>> On 2/4/2016 1:37 PM, Aki Balogh wrote:
>>> > Specifically, they suggest getting clusterstate.json. But I've tried
>>> that
>>> > and when I get that file, I only get an empty file {}
>>> >
>>> > Is there another way to ask Zookeeper to cover the missing hash range?
>>>
>>> Solr 5.x changed how the clusterstate is managed. The
>>> /clusterstate.json file is empty, just as you have noticed. You'll find
>>> the actual clusterstate inside each collection path, in a file named
>>> "state.json".
>>>
>>> Here's what it will look like in the Cloud->Tree section of the admin UI:
>>>
>>> https://www.dropbox.com/s/1964mnkuds1uh3d/solr5-state.json.png?dl=0
>>> <https://t.yesware.com/tt/506312808dab13214164f92fbcf5714d3ce38c6b/659fcec96904fac56f9fd004afb59c85/8d983cbf7ca8a8b82e589197599cb5a9/www.dropbox.com/s/1964mnkuds1uh3d/solr5-state.json.png?dl=0>
>>>
>>> If any of those guides you found are hosted on an official apache.org
>>> <http://t.yesware.com/tt/506312808dab13214164f92fbcf5714d3ce38c6b/659fcec96904fac56f9fd004afb59c85/9b616471fb9c3db091f049a0dd55ba90/apache.org>
>>> website (and do not explicitly mention the 4.x version they apply to),
>>> then that's our job to update, but third-party information will be the
>>> responsibility of the person who posted it.
>>>
>>> Thanks,
>>> Shawn
>>>
>>>
>>
