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 "mike st. john" <ms...@gmail.com> on 2013/03/04 18:44:28 UTC
Having an issue where atomic updates are treated as new docs running
in solrcloud on 4.1
Hi,
running tomcat , solr 4.1 distributed 4 shards 2 replicas per shard.
Everything works fine searching, but i'm trying to use this instance as
a nosql solution as well. What i've noticed , when i send a partial
update i'll receive "missing required field" if the document is not
located on the url i'm sending the update to, implying that its not
distributing the updates to the correct servers.
thanks for any help.
Mike
Re: Having an issue where atomic updates are treated as new docs running in solrcloud on 4.1
Posted by Mark Miller <ma...@gmail.com>.
On Mar 4, 2013, at 1:32 PM, Michael Della Bitta <mi...@appinions.com> wrote:
> Are you sure sending it to the collection URL as opposed to one of the
> shard URLs?
FYI, it should work the same either way.
>
> If you go to the Cloud tab, click on Tree, and then click on
> clusterstate.json, what is the value for "router" for that collection?
Good call!
- Mark
Re: Having an issue where atomic updates are treated as new docs
running in solrcloud on 4.1
Posted by "mike st. john" <ms...@gmail.com>.
thanks mark.
That worked great.
-Mike
Mark Miller wrote:
>
> Honestly, I'm not sure. Yonik did some testing around upgrading from
> 4.0 to 4.1 and said this was fine - but it sounds like perhaps there
> are some hitches.
>
> - Mark
>
> On Mar 4, 2013, at 3:35 PM, "mike st. john"<ms...@gmail.com> wrote:
>
>>
>> Mark,
>>
>> the odd piece here i think was, this was a 4.0 collection numShards=4
>> etc etc.
>>
>> moved to 4.1, i would assume the doc router would have been set to
>> compositeId, not implicit, or is the move from 4.0 to 4.1 a complete
>> rebuild from the collections up?
>>
>> -Mike
>>
>> Mark Miller wrote:
>>>
>>> On Mar 4, 2013, at 3:27 PM, Michael Della
>>> Bitta<mi...@appinions.com> wrote:
>>>
>>>>
>>>> I personally don't know of one other than starting over with a new
>>>> collection, but I'd love to be proven wrong, because I'm actually
>>>> in the
>>>> same boat as you!
>>>
>>>
>>> I think it might be possible by using a zookeeper tool to edit
>>> clusterstate.json (i like using the zk eclipse plugin for this type
>>> of thing).
>>>
>>> If you create a new collection with the same number of shards and be
>>> sure to specify num shards, you will see the hash ranges that should
>>> be used for each shard. Try updating the clusterstate.json to match
>>> - with the right router and hash ranges.
>>>
>>> - Mark
>>
>
Re: Having an issue where atomic updates are treated as new docs running in solrcloud on 4.1
Posted by Mark Miller <ma...@gmail.com>.
Honestly, I'm not sure. Yonik did some testing around upgrading from 4.0 to 4.1 and said this was fine - but it sounds like perhaps there are some hitches.
- Mark
On Mar 4, 2013, at 3:35 PM, "mike st. john" <ms...@gmail.com> wrote:
> Mark,
>
> the odd piece here i think was, this was a 4.0 collection numShards=4 etc etc.
>
> moved to 4.1, i would assume the doc router would have been set to compositeId, not implicit, or is the move from 4.0 to 4.1 a complete rebuild from the collections up?
>
> -Mike
>
> Mark Miller wrote:
>>
>> On Mar 4, 2013, at 3:27 PM, Michael Della Bitta<mi...@appinions.com> wrote:
>>
>>>
>>> I personally don't know of one other than starting over with a new
>>> collection, but I'd love to be proven wrong, because I'm actually in the
>>> same boat as you!
>>
>>
>> I think it might be possible by using a zookeeper tool to edit clusterstate.json (i like using the zk eclipse plugin for this type of thing).
>>
>> If you create a new collection with the same number of shards and be sure to specify num shards, you will see the hash ranges that should be used for each shard. Try updating the clusterstate.json to match - with the right router and hash ranges.
>>
>> - Mark
Re: Having an issue where atomic updates are treated as new docs
running in solrcloud on 4.1
Posted by "mike st. john" <ms...@gmail.com>.
Mark,
the odd piece here i think was, this was a 4.0 collection numShards=4
etc etc.
moved to 4.1, i would assume the doc router would have been set to
compositeId, not implicit, or is the move from 4.0 to 4.1 a complete
rebuild from the collections up?
-Mike
Mark Miller wrote:
>
> On Mar 4, 2013, at 3:27 PM, Michael Della
> Bitta<mi...@appinions.com> wrote:
>
>>
>> I personally don't know of one other than starting over with a new
>> collection, but I'd love to be proven wrong, because I'm actually in the
>> same boat as you!
>
>
> I think it might be possible by using a zookeeper tool to edit
> clusterstate.json (i like using the zk eclipse plugin for this type of
> thing).
>
> If you create a new collection with the same number of shards and be
> sure to specify num shards, you will see the hash ranges that should
> be used for each shard. Try updating the clusterstate.json to match -
> with the right router and hash ranges.
>
> - Mark
Re: Having an issue where atomic updates are treated as new docs running in solrcloud on 4.1
Posted by Mark Miller <ma...@gmail.com>.
On Mar 4, 2013, at 3:27 PM, Michael Della Bitta <mi...@appinions.com> wrote:
> I personally don't know of one other than starting over with a new
> collection, but I'd love to be proven wrong, because I'm actually in the
> same boat as you!
I think it might be possible by using a zookeeper tool to edit clusterstate.json (i like using the zk eclipse plugin for this type of thing).
If you create a new collection with the same number of shards and be sure to specify num shards, you will see the hash ranges that should be used for each shard. Try updating the clusterstate.json to match - with the right router and hash ranges.
- Mark
Re: Having an issue where atomic updates are treated as new docs
running in solrcloud on 4.1
Posted by Michael Della Bitta <mi...@appinions.com>.
I personally don't know of one other than starting over with a new
collection, but I'd love to be proven wrong, because I'm actually in the
same boat as you!
On Mar 4, 2013 6:09 PM, "mike st. john" <ms...@gmail.com> wrote:
> Hi michael,
>
> ah, thats seems to be the issue, its set to implicit.
>
> This install originally was a 4.0 install, when it moved to 4.1 , the
> problems started.
>
> Is there an easy way to change the router to compositeId?
>
>
> -Mike
>
> Michael Della Bitta wrote:
>
>>
>> Hi Mike,
>>
>> Are you sure sending it to the collection URL as opposed to one of the
>> shard URLs?
>>
>> If you go to the Cloud tab, click on Tree, and then click on
>> clusterstate.json, what is the value for "router" for that collection?
>>
>>
>> Michael Della Bitta
>>
>> ------------------------------**------------------
>> Appinions
>> 18 East 41st Street, 2nd Floor
>> New York, NY 10017-6271
>>
>> www.appinions.com
>>
>> Where Influence Isn’t a Game
>>
>>
>> On Mon, Mar 4, 2013 at 12:44 PM, mike st. john<ms...@gmail.com> wrote:
>>
>>>
>>> Hi,
>>>
>>> running tomcat , solr 4.1 distributed 4 shards 2 replicas per shard.
>>> Everything works fine searching, but i'm trying to use this instance as a
>>> nosql solution as well. What i've noticed , when i send a partial update
>>> i'll receive "missing required field" if the document is not located on
>>> the
>>> url i'm sending the update to, implying that its not distributing the
>>> updates to the correct servers.
>>>
>>> thanks for any help.
>>>
>>>
>>> Mike
>>>
>>
Re: Having an issue where atomic updates are treated as new docs
running in solrcloud on 4.1
Posted by "mike st. john" <ms...@gmail.com>.
Hi michael,
ah, thats seems to be the issue, its set to implicit.
This install originally was a 4.0 install, when it moved to 4.1 , the
problems started.
Is there an easy way to change the router to compositeId?
-Mike
Michael Della Bitta wrote:
>
> Hi Mike,
>
> Are you sure sending it to the collection URL as opposed to one of the
> shard URLs?
>
> If you go to the Cloud tab, click on Tree, and then click on
> clusterstate.json, what is the value for "router" for that collection?
>
>
> Michael Della Bitta
>
> ------------------------------------------------
> Appinions
> 18 East 41st Street, 2nd Floor
> New York, NY 10017-6271
>
> www.appinions.com
>
> Where Influence Isn’t a Game
>
>
> On Mon, Mar 4, 2013 at 12:44 PM, mike st. john<ms...@gmail.com> wrote:
>>
>> Hi,
>>
>> running tomcat , solr 4.1 distributed 4 shards 2 replicas per shard.
>> Everything works fine searching, but i'm trying to use this instance as a
>> nosql solution as well. What i've noticed , when i send a partial update
>> i'll receive "missing required field" if the document is not located
>> on the
>> url i'm sending the update to, implying that its not distributing the
>> updates to the correct servers.
>>
>> thanks for any help.
>>
>>
>> Mike
Re: Having an issue where atomic updates are treated as new docs
running in solrcloud on 4.1
Posted by Michael Della Bitta <mi...@appinions.com>.
Hi Mike,
Are you sure sending it to the collection URL as opposed to one of the
shard URLs?
If you go to the Cloud tab, click on Tree, and then click on
clusterstate.json, what is the value for "router" for that collection?
Michael Della Bitta
------------------------------------------------
Appinions
18 East 41st Street, 2nd Floor
New York, NY 10017-6271
www.appinions.com
Where Influence Isn’t a Game
On Mon, Mar 4, 2013 at 12:44 PM, mike st. john <ms...@gmail.com> wrote:
> Hi,
>
> running tomcat , solr 4.1 distributed 4 shards 2 replicas per shard.
> Everything works fine searching, but i'm trying to use this instance as a
> nosql solution as well. What i've noticed , when i send a partial update
> i'll receive "missing required field" if the document is not located on the
> url i'm sending the update to, implying that its not distributing the
> updates to the correct servers.
>
> thanks for any help.
>
>
> Mike