Hello
My crash.log is continually filling up with the following message after
replacing a node:
2017-06-22 08:06:05 =CRASH REPORT
crasher:
initial call: riak_kv_index_hashtree:init/1
pid: <0.16663.2>
registered_name: []
exception exit:
{{function_clause,[{riak_core_bucket_
Hi,
I'm not sure but looking at the exception and the code you get function
clause error because you have the first argument being '$deleted' and the
function guard expects lists as arguments
https://github.com/basho/riak_core/blob/master/src/riak_core_bucket_props.erl#L129
The reason for it bei
Hi,
I see now there is support for 2i which we needed in order to migrate to
2.x, there was another issue with the old client which forced us to
modify the client, such issue was related to the following, let me put
an example:
public class POJO {
@RiakKey
public String getKey() {
/
Also, a property annotated with a Riak annotation was kept in the Json
only if it has been explicitly annotated with @JsonProperty or has not
been annotated with a Riak property.
This was accomplished with the following code from the old client:
static {
RIAK_ANNOTATIONS.add(RiakK
Hello
force-deleted a node but I made no modification to bucket properties.
From: jo...@s2hc.com [mailto:jo...@s2hc.com] On Behalf Of Johan Sommerfeld
Sent: 22 June 2017 09:30
To: Mark Richard Thomas
Cc: riak-users@lists.basho.com
Subject: [IE] Re: Continuous Crash Report
Hi,
I'm not sure but l
Hi List,
We have a standard riak cluster with 5 nodes and at the minute the traffic
levels are fairly low. Each of our application nodes has 25 client
connections, 5 to each riak node which get selected in a round robin.
Our application level requests involve multiple riak requests so our
traffic
Anybody seen this in their logs?
yz_solrq_sup:stop_queue_pair:130 Stopping solrq supervisor for index
<<"search1">>
Searching using the index still works, however I am getting log notices
for most my indexes?
If you know, please tell me... Thank you!
Sincerely,
Robert
I haven't used bucket types that much so have no real idea of why it
thinks that a bucket type is deleted.
If you read the error log it seem like {name
{<<"commercial">>,<<"commercial_systest">>}}. As I said I'm not that
familiar wit bucket types but having a tuple as name feels odd. What
bucket t
It's pretty strange that you are seeing no search latency measurements on node
5. Are you sure your round robining is working? Are you favoring node 1?
In general, I don't think which node you hit for query should make a
difference, but I'd have to stare at the code some to be sure. In essenc
This might be a relatively benign message, which might be better at debug scope
than info scope. This would have been introduced in 2.0.8 or 2.2.2 or later.
Essentially, there are solq supervisors for each partition/index pair (for each
partition on a node), and when these supervisors start or
10 matches
Mail list logo