Robert,
What Keith said is misleading -- that key cache was solely in the Ruby client
driver and not part of Riak itself.
In Riak, deletes have two phases; in the first, so-called "tombstones" are
written to the partitions that own replicas of the key. The tombstone has
special metadata marki
Robert -
Until a source code change a few days ago, riak would by default cache the keys
reported to be in a bucket, so after fetching them once they would not be
updated after deletions, additions, etc. The key is indeed gone, but the keys
API did not report the change.
If you go to the mess
Hi,
When deleting a key from a bucket I'm noticing that the object associated with
the key is gone but the key itself is still sticking around. I loop though all
of the keys in a bucket and then call delete on each one, the object for the
key is then gone so if I try to get the object for that
Gordon,
Great news! Much appreciated.
Gilbert
On Tue, May 31, 2011 at 2:25 PM, Gordon Tillman wrote:
> Howdy Gilbert,
>
> Hey we are testing a fix now. If this works I will send you a copy of the
> update file.
>
> --gordon
>
>
> On May 31, 2011, at 12:55 , Gilbert Glåns wrote:
>
>> Hi Gordo
Howdy Gilbert,
Hey we are testing a fix now. If this works I will send you a copy of the
update file.
--gordon
On May 31, 2011, at 12:55 , Gilbert Glåns wrote:
> Hi Gordon,
> Thank you for sharing the information. We are seeing the same exact
> type of behavior from our search cluster. I h
Hi David,
This looks similar to bug 989:
https://issues.basho.com/show_bug.cgi?id=989
Can you remove all mr_queue data files and restart the node?
rm data/mr_queue/*
This issue has been fixed as of Riak 0.14.1. You can perform a rolling
upgrade if you'd like to upgrade your Riak cluster:
http://
Hi David,
Can you confirm you have built Riak from source? What branch/tag are you
using? What version of Erlang are you using?
I would suggest undoing the "root:root" ownership change. Do you have any
data in the Riak instance or is this a fresh install? How are you starting
Riak (the exact comm
Hi Dan,
There are no other beam processes running. The only thing running that is
related to riak is "riak/erts-5.7.5/bin/epmd -daemon".
David
From: Dan Reverri [mailto:d...@basho.com]
Sent: Tuesday, May 31, 2011 12:37 PM
To: David Mitchell
Cc: riak-users@lists.basho.com
Subject: Re: riak no
Hi Gordon,
Thank you for sharing the information. We are seeing the same exact
type of behavior from our search cluster. I have tracked the
problem(s) though the query system. It looks like the mailboxes we
are both seeing are "abandoned" and / or the messages are never
matched within the Erlang
Hi David,
Can you check to see if you have any beam processes running (perhaps another
Riak instance)?
Thanks,
Dan
Daniel Reverri
Developer Advocate
Basho Technologies, Inc.
d...@basho.com
On Tue, May 31, 2011 at 9:17 AM, David Mitchell
wrote:
> Hi, one of the riak nodes is not starting. I a
Hi, one of the riak nodes is not starting. I am getting
{badmatch,already_exists} in sasl-error.log.
At first, I was getting 'eaccess' errors, so I changed all of the files to be
owned by "root:root". Now, I am getting,
{badmatch,already_exists}.
In, erlang.log.1, I see:
[{application,riak_k
Actually, I think it should be part of the wiki, and have opened an issue to
that effect. https://github.com/basho/riak_wiki/issues/106
Sean Cribbs
Developer Advocate
Basho Technologies, Inc.
http://basho.com/
On May 31, 2011, at 12:05 PM, Mark Phillips wrote:
> Hey Bob,
>
> Any objections if
Hey Bob,
Any objections if I clean this up and add it to the "Other" section of
Riak Function Contrib? It's clearly not a function, but I think others
would find this useful (as Scott did) as a point of reference.
http://contrib.basho.com/other-functions.html
Let me know and I'll throw together
Howdy Gilbert,
I reproduced the issue this morning and then ran the command that you specified
on two of the non-empty mailboxes.
The output from that is posted here:
https://gist.github.com/1000735
Please let me know if this corresponds to the issue that you are seeing.
Thank you,
--gordon
14 matches
Mail list logo