Hi Fred,
Thanks for internal call tips, I'll dig deeper!
I've attached recent results of `riak-admin search aae-status` from all
nodes.
On 5 April 2016 at 22:41, Fred Dushin wrote:
> Hi Oleksiy,
>
> I assume you are getting this information through riak-admin. Can you
> post the results here
Hi Oleksiy,
I assume you are getting this information through riak-admin. Can you post the
results here?
If you want to dig deeper, you can probe the individual hash trees for their
build time. I will paste a few snippets of erlang here, which I am hoping you
can extend to use with list comp
How can I check that AAE trees have expired? Yesterday I ran "
riak_core_util:rpc_every_member_ann(yz_entropy_mgr, expire_trees, [],
5000)." on each node (just to be sure). Still today I see that on 3 nodes
(of 5) all entropy tress and all last AAE exchanges are older than 20 days.
On 4 April 201
Hello,
I have fixed it.
Issue was instance private ip.
I have changed below variable :
listener.protobuf.internal = :8087
It fixed the issue.
--
View this message in context:
http://riak-users.197444.n3.nabble.com/cannot-start-solr-no-logs-tp4033816p4034123.html
Sent from the Riak Users
Hello,
I tried below steps but no luck.
#rm -rf /var/lib/riak/ring/*
#riak start
error.log
2016-04-05 08:03:11.845 [error] <0.538.0> gen_server yz_solr_proc terminated
with reason: {"solr OS process exited",1}
2016-04-05 08:03:11.845 [error] <0.538.0> CRASH REPORT Process yz_solr_proc
with 0 n
Hello,
Yes, I am trying with search = on and its not starting. (search = off
starting fine)
Os is debian 8 .
crash.log
** Generic server riak_core_capability terminating
** Last message in was
{register,{riak_core,vnode_routing},{capability,[proxy,legacy],legacy,{riak_core,legacy_vnode_routin
