You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-user@lucene.apache.org by Brett Hoerner <br...@bretthoerner.com> on 2013/11/25 17:18:05 UTC
Trouble with manually routed collection after upgrade to 4.6
Hi, I've been using a collection on Solr 4.5.X for a few weeks and just did
an upgrade to 4.6 and am having some issues.
First: this collection is, I guess, implicitly routed. I do this for every
document insert using SolrJ:
document.addField("_route_", shardId)
After upgrading the servers to 4.6 I now get the following on every
insert/delete when using either SolrJ 4.5.1 or 4.6:
org.apache.solr.common.SolrException: No active slice servicing hash code
17b9dff6 in DocCollection
In the clusterstate *none* of my shards have a range set (they're all
null), but I thought this would be expected since I do routing myself.
Did the upgrade change something here? I didn't see anything related to
this in the upgrade notes.
Thanks,
Brett
Re: Trouble with manually routed collection after upgrade to 4.6
Posted by Shalin Shekhar Mangar <sh...@gmail.com>.
That's not good. I'll investigate.
On Mon, Nov 25, 2013 at 10:29 PM, Brett Hoerner <br...@bretthoerner.com> wrote:
> Think I got it. For some reason this was in my clusterstate.json after the
> upgrade (note that I was using 4.5.X just fine previously...):
>
> "router": {
> "name": "compositeId"
> },
>
> I stopped all my nodes and manually edited this to me "implicit" (is there
> a tool for this? I've always done it manually), started the cluster up
> again and it's all good now.
>
>
>
> On Mon, Nov 25, 2013 at 10:38 AM, Brett Hoerner <br...@bretthoerner.com>wrote:
>
>> Here's my clusterstate.json:
>>
>> https://gist.github.com/bretthoerner/a8120a8d89c93f773d70
>>
>>
>> On Mon, Nov 25, 2013 at 10:18 AM, Brett Hoerner <br...@bretthoerner.com>wrote:
>>
>>> Hi, I've been using a collection on Solr 4.5.X for a few weeks and just
>>> did an upgrade to 4.6 and am having some issues.
>>>
>>> First: this collection is, I guess, implicitly routed. I do this for
>>> every document insert using SolrJ:
>>>
>>> document.addField("_route_", shardId)
>>>
>>> After upgrading the servers to 4.6 I now get the following on every
>>> insert/delete when using either SolrJ 4.5.1 or 4.6:
>>>
>>> org.apache.solr.common.SolrException: No active slice servicing hash
>>> code 17b9dff6 in DocCollection
>>>
>>> In the clusterstate *none* of my shards have a range set (they're all
>>> null), but I thought this would be expected since I do routing myself.
>>>
>>> Did the upgrade change something here? I didn't see anything related to
>>> this in the upgrade notes.
>>>
>>> Thanks,
>>> Brett
>>>
>>
>>
--
Regards,
Shalin Shekhar Mangar.
Re: Trouble with manually routed collection after upgrade to 4.6
Posted by Brett Hoerner <br...@bretthoerner.com>.
Think I got it. For some reason this was in my clusterstate.json after the
upgrade (note that I was using 4.5.X just fine previously...):
"router": {
"name": "compositeId"
},
I stopped all my nodes and manually edited this to me "implicit" (is there
a tool for this? I've always done it manually), started the cluster up
again and it's all good now.
On Mon, Nov 25, 2013 at 10:38 AM, Brett Hoerner <br...@bretthoerner.com>wrote:
> Here's my clusterstate.json:
>
> https://gist.github.com/bretthoerner/a8120a8d89c93f773d70
>
>
> On Mon, Nov 25, 2013 at 10:18 AM, Brett Hoerner <br...@bretthoerner.com>wrote:
>
>> Hi, I've been using a collection on Solr 4.5.X for a few weeks and just
>> did an upgrade to 4.6 and am having some issues.
>>
>> First: this collection is, I guess, implicitly routed. I do this for
>> every document insert using SolrJ:
>>
>> document.addField("_route_", shardId)
>>
>> After upgrading the servers to 4.6 I now get the following on every
>> insert/delete when using either SolrJ 4.5.1 or 4.6:
>>
>> org.apache.solr.common.SolrException: No active slice servicing hash
>> code 17b9dff6 in DocCollection
>>
>> In the clusterstate *none* of my shards have a range set (they're all
>> null), but I thought this would be expected since I do routing myself.
>>
>> Did the upgrade change something here? I didn't see anything related to
>> this in the upgrade notes.
>>
>> Thanks,
>> Brett
>>
>
>
Re: Trouble with manually routed collection after upgrade to 4.6
Posted by Brett Hoerner <br...@bretthoerner.com>.
Here's my clusterstate.json:
https://gist.github.com/bretthoerner/a8120a8d89c93f773d70
On Mon, Nov 25, 2013 at 10:18 AM, Brett Hoerner <br...@bretthoerner.com>wrote:
> Hi, I've been using a collection on Solr 4.5.X for a few weeks and just
> did an upgrade to 4.6 and am having some issues.
>
> First: this collection is, I guess, implicitly routed. I do this for every
> document insert using SolrJ:
>
> document.addField("_route_", shardId)
>
> After upgrading the servers to 4.6 I now get the following on every
> insert/delete when using either SolrJ 4.5.1 or 4.6:
>
> org.apache.solr.common.SolrException: No active slice servicing hash
> code 17b9dff6 in DocCollection
>
> In the clusterstate *none* of my shards have a range set (they're all
> null), but I thought this would be expected since I do routing myself.
>
> Did the upgrade change something here? I didn't see anything related to
> this in the upgrade notes.
>
> Thanks,
> Brett
>