Riak 2.0.4 Search AAE

2015-02-18 Thread Steve Garon
Hi all,

I seem to have trouble with aae on riak 2.0.4. Specifically the search aae.
When I run the command 'riak-admin aae-status' everything seems fine but if
I run the same command for search (riak-admin search aae-status) it seem
like the search entropy trees have never been built and never do. All I get
on every field is --.

Any command I can run to force the trees to be built so I get consistent
search results?

Steve
___
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com


Re: Riak 2.0.4 Search AAE

2015-02-18 Thread Zeeshan Lakhani
Hey Steve, I’ve run AAE manually by running `riak attach` on a running node and 
calling 
https://github.com/basho/yokozuna/blob/develop/src/yz_entropy_mgr.erl#L142 
 
(yz_entropy_mgr:init([])).

Nonetheless, to take a closer look, is there any data within search’s 
data-directory? You can find out by looking in ./data/yz_anti_entropy (on any 
of nodes). You can find more info in our docs, 
http://docs.basho.com/riak/latest/ops/advanced/configs/search/ 
, about 
search’s config settings.
 
Zeeshan Lakhani
programmer | 
software engineer at @basho | 
org. member/founder of @papers_we_love |
twitter => @zeeshanlakhani

> On Feb 18, 2015, at 9:03 AM, Steve Garon  wrote:
> 
> Hi all, 
> 
> I seem to have trouble with aae on riak 2.0.4. Specifically the search aae. 
> When I run the command 'riak-admin aae-status' everything seems fine but if I 
> run the same command for search (riak-admin search aae-status) it seem like 
> the search entropy trees have never been built and never do. All I get on 
> every field is --. 
> 
> Any command I can run to force the trees to be built so I get consistent 
> search results?  
> 
> Steve
> ___
> riak-users mailing list
> riak-users@lists.basho.com
> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com

___
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com


Riak 2.0.4 AAE spinning

2015-02-18 Thread Chris Read
We recently upgraded to Riak 2.0.4 and started seeing the thousands of the
following error in one of our nodes:

2015-02-18 07:48:16.652 [error] <0.23966.264> CRASH REPORT Process
<0.23966.264> with 0 neighbours exited with reason: no match of right hand
value {error,{db_open,"IO error: lock
/srv/riak-0/data/anti_entropy/548063113999088594326381812268606132370974703616/LOCK:
already held by process"}} in hashtree:new_segment_store/2 line 555 in
gen_server:init_it/6 line 328
2015-02-18 07:48:16.652 [info]
<0.27823.1997>@riak_kv_vnode:maybe_create_hashtrees:178
riak_kv/548063113999088594326381812268606132370974703616: unable to start
index_hashtree: {error,{{badmatch,{error,{db_open,"IO error: lock
/srv/riak-0/data/anti_entropy/548063113999088594326381812268606132370974703616/LOCK:
already held by
process"}}},[{hashtree,new_segment_store,2,[{file,"src/hashtree.erl"},{line,555}]},{hashtree,new,2,[{file,"src/hashtree.erl"},{line,224}]},{riak_kv_index_hashtree,do_new_tree,2,[{file,"src/riak_kv_index_hashtree.erl"},{line,560}]},{lists,foldl,3,[{file,"lists.erl"},{line,1248}]},{riak_kv_index_hashtree,init_trees,2,[{file,"src/riak_kv_index_hashtree.erl"},{line,430}]},{riak_kv_index_hashtree,init,1,[{file,"src/riak_kv_index_hashtree.erl"},{line,255}]},{gen_server,init_it,6,[{file,"gen_server.erl"},{line,304}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,239}]}]}}

This correlates with a massive spike in GET requests on the three nodes
that own the affected vnode.

Anyone have any ideas?

Chris
___
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com


Re: Riak 2.0.4 Search AAE

2015-02-18 Thread Steve Garon
Hey Zeeshan,

There is tons of data in yz_anti_entropy. Should I delete it before running
your command?




Steve

On 18 February 2015 at 09:49, Zeeshan Lakhani  wrote:

> Hey Steve, I’ve run AAE manually by running `riak attach` on a running
> node and calling
> https://github.com/basho/yokozuna/blob/develop/src/yz_entropy_mgr.erl#L142
>  (yz_entropy_mgr:init([])).
>
> Nonetheless, to take a closer look, is there any data within search’s
> data-directory? You can find out by looking in ./data/yz_anti_entropy (on
> any of nodes). You can find more info in our docs,
> http://docs.basho.com/riak/latest/ops/advanced/configs/search/, about
> search’s config settings.
>
> Zeeshan Lakhani
> programmer |
> software engineer at @basho |
> org. member/founder of @papers_we_love |
> twitter => @zeeshanlakhani
>
> On Feb 18, 2015, at 9:03 AM, Steve Garon  wrote:
>
> Hi all,
>
> I seem to have trouble with aae on riak 2.0.4. Specifically the search
> aae. When I run the command 'riak-admin aae-status' everything seems fine
> but if I run the same command for search (riak-admin search aae-status) it
> seem like the search entropy trees have never been built and never do. All
> I get on every field is --.
>
> Any command I can run to force the trees to be built so I get consistent
> search results?
>
> Steve
>  ___
> riak-users mailing list
> riak-users@lists.basho.com
> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
>
>
>
___
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com


Re: Riak 2.0.4 Search AAE

2015-02-18 Thread Zeeshan Lakhani
Well, that means that it is storing AAE data. Are you have consistency issues 
between what’s in KV (the canonical source) and Search/Solr? 

You can remove the data on every node by using 
`riak_core_util:rpc_every_member_ann(yz_entropy_mgr, clear_trees, [], 
infinity)` as well and then try to initialize AAE again. As you can see in this 
part of Ryan’s vid, https://www.youtube.com/watch?v=ETJqu5SmwOc#t=2290 
 (and our constants in 
https://github.com/basho/yokozuna/blob/47214a66e07fdfd04bbaae6bdd18580f87693edf/include/yokozuna.hrl#L187
 
),
 you can, via `riak attach`, update the  environment vars of entropy_expire, 
tick, and concurrency to speed up AAE in your testing of this bug.


Zeeshan Lakhani
programmer | 
software engineer at @basho | 
org. member/founder of @papers_we_love |
twitter => @zeeshanlakhani

> On Feb 18, 2015, at 1:21 PM, Steve Garon  wrote:
> 
> Hey Zeeshan, 
> 
> There is tons of data in yz_anti_entropy. Should I delete it before running 
> your command? 
> 
> 
> 
> 
> Steve
> 
> On 18 February 2015 at 09:49, Zeeshan Lakhani  > wrote:
> Hey Steve, I’ve run AAE manually by running `riak attach` on a running node 
> and calling 
> https://github.com/basho/yokozuna/blob/develop/src/yz_entropy_mgr.erl#L142 
>  
> (yz_entropy_mgr:init([])).
> 
> Nonetheless, to take a closer look, is there any data within search’s 
> data-directory? You can find out by looking in ./data/yz_anti_entropy (on any 
> of nodes). You can find more info in our docs, 
> http://docs.basho.com/riak/latest/ops/advanced/configs/search/ 
> , about 
> search’s config settings.
>  
> Zeeshan Lakhani
> programmer | 
> software engineer at @basho | 
> org. member/founder of @papers_we_love |
> twitter => @zeeshanlakhani
> 
>> On Feb 18, 2015, at 9:03 AM, Steve Garon > > wrote:
>> 
>> Hi all, 
>> 
>> I seem to have trouble with aae on riak 2.0.4. Specifically the search aae. 
>> When I run the command 'riak-admin aae-status' everything seems fine but if 
>> I run the same command for search (riak-admin search aae-status) it seem 
>> like the search entropy trees have never been built and never do. All I get 
>> on every field is --. 
>> 
>> Any command I can run to force the trees to be built so I get consistent 
>> search results?  
>> 
>> Steve
>> ___
>> riak-users mailing list
>> riak-users@lists.basho.com 
>> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com 
>> 
> 
> 

___
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com


Yokozuna unpredictable result count

2015-02-18 Thread Cezary Kosko
Hi,

I've got a search index, and I'd like to run mapred job against that index.
The thing is, for a search query that should return exactly one result, I
sometimes (not always, yet not rarely) get none, i.e. the mapred job
returns an empty list instead of, say, a list containing a single object.
Did this only happen some time after uploading the data and then was
consistently giving the right results, I wouldn't object. However, it's
kind of an on-and-off situation - I get proper results, but then for a
brief period of time I don't and so on.

I've read on a solr doc page that specifying a timeAllowed parameter in the
query can give it longer to gather results and help, but that can't be
specified in a mapred definition, or can it?

Is there anything else I can look for?

The data I'm querying is of the CRDT map-of-sets type, should that be of
any relevance.

Kind regards,
Cezary
___
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com