Hello.
After update 2.0.4-1 we start to see lot of errors, like this:
Supervisor riak_pipe_fitting_sup had child undefined started with
riak_pipe_fitting:start_link() at <0.5490.42> exit with reason noproc in
context shutdown_error
Sasl.log:
=SUPERVISOR REPORT 21-Jan-2015::17:53:46 ===
Each request to riak search return different results. It's return different
numFound.
I use request like this:
http://localhost:8098/search/query/assets?wt=json&q=type:*&sort=_yz_rk%20asc
If add start offset it can return:
http://localhost:8098/search/query/assets?wt=json&q=type:*&sort=_yz_rk%2
; Thanks.
>
> Zeeshan Lakhani
> programmer |
> software engineer at @basho |
> org. member/founder of @papers_we_love | paperswelove.org
> twitter => @zeeshanlakhani
>
> On Mar 12, 2015, at 5:59 AM, Roma Lakotko wrote:
>
> Each request to riak search return diff
every_member_ann(application, get_env, [riak_kv,
> anti_entropy_concurrency],infinity).
> riak_core_util:rpc_every_member_ann(application, get_env, [yokozuna,
> anti_entropy_tick],infinity).
> ```
>
> … on any of the nodes. Query coverage is R=1, but the values should be
> replicated acro
No, its simple riak search http request.
12 марта 2015 г. 18:54 пользователь "Zeeshan Lakhani"
написал:
> Are you running mapreduce with Solr queries?
>
>
> On Mar 12, 2015, at 11:50 AM, Roma Lakotko wrote:
>
> I don't see any solr errors. But each 10-20 minute
each node?
And, is this bug already patched? Or in future i can have same problem
after add/remove nodes?
Thanks,
Roman Lakotko.
2015-03-12 18:56 GMT+03:00 Roma Lakotko :
> No, its simple riak search http request.
> 12 марта 2015 г. 18:54 пользователь "Zeeshan Lakhani"
> напи
I repeat same on production cluster, it's work. Thanks.
2015-03-13 10:23 GMT+03:00 Roma Lakotko :
> Hello.
>
> Good news. After i remove folder, and start yz_entropy_mgr:init([]) and
> then re-save objects it's start to return correct numFound (test on 2
> buckets, abou
