Hi Nico,
Its unclear riak-admin status eventually calls riak_kv_stat:get_stats
which states
%% mem_total
%% The first element of the tuple returned by
%% {@link memsup:get_memory_data/0}.
%%
%% mem_allocated
%% The second element of the tuple returned by
%% {@link memsup:get_
On Mar 23, 2011, at 2:25 PM, Jon Brisbin wrote:
> I personally don't like using ambiguous short names. I get that you can
> technically distinguish things by package name but using a simple name that
> is very common isn't good for code readability. "RiakEntry" is unambiguous,
> self-documenti
Sorry, I don't have a lot of time right now. I'll try to write a more
detailed response later.
>>> With a few hours of investigation today, your patch is looking
>>> promising. Maybe you can give some more detail on what you did in your
>>> experiments a few months ago?
I'll try to write somethin
Hi Anthony,
are you sure you are not including the filesystem cache in your
mem_allocated values? It will grow to use all of the free memory or the
total size of your bitcask data files, whichever is smaller.
We have about 100Mio keys per node, and riak uses about 7GB of RAM.
Cheers,
Nico
O
After reading todays recap, I am a bit unsure:
5) Q --- Would Riak handle an individual vnode failure the same way as
an entire node failure? (from grourk via #riak)
A --- Yes. The request to that vnode would fail and will be routed
to the next available vnode
Is it really handled the sam
Hi Greg,
I don't think the vnodes will always die. I have seen some situations
(disk full, filesystem becoming read only due to device errors,
corrupted bitcask files after a mashine crash) where the vnode did not
crash, but the get and/or put requests returned errors.
Even if the process cras
Hi Jon,
A replied to Kresten, and before I managed you replied more succinctly with a
lot of what I had to say.
On 23 Mar 2011, at 21:25, Jon Brisbin wrote:
> I personally don't like using ambiguous short names. I get that you can
> technically distinguish things by package name but using a si
Afternoon, Evening, Morning to All -
For today's Recap: slides from last night's Riak Meetup, a few
questions and gists from #riak and more.
Enjoy.
Mark
Community Manager
Basho Technologies
wiki.basho.com
twitter.com/pharkmillups
Riak Recap for March 21 - 22
1) @coda just posted the sli
Hi Joe,
With a few hours of investigation today, your patch is looking promising. Maybe
you can give some more detail on what you did in your experiments a few months
ago?
What I did was set up a Ubuntu VM with three loopback file systems. Then built
Riak 0.14.1 with your patch, configured as
So a question about when to add new nodes. I'm looking at the output of
this script and the output of riak-admin status to attempt to figure out
if it's time to grow a cluster.
I have 4 nodes 1024 partitions replication factor 3, currently with a
single bitcask single bucket where both the key an
Thanks for the reply and thoughts, mine below inline.
On 23 Mar 2011, at 20:21, Kresten Krab Thorup wrote:
> From the client side, the moniker RiakObject is actually not too good. In
> technical terms, it is of cause a riak_object - but to a Java programmer, it
> doesn't feel right for it to
Record or Document are alternatives I'd prefer over Entry (prefixed
with Riak or not)
On Wed, Mar 23, 2011 at 2:25 PM, Jon Brisbin wrote:
>
> On Mar 23, 2011, at 3:21 PM, Kresten Krab Thorup wrote:
>
> From the client side, the moniker RiakObject is actually not too good. In
> technical terms, i
On Mar 23, 2011, at 3:21 PM, Kresten Krab Thorup wrote:
> From the client side, the moniker RiakObject is actually not too good. In
> technical terms, it is of cause a riak_object - but to a Java programmer, it
> doesn't feel right for it to have that name. It's more like a
> KeyValueHolder
Thanks for the super quick response - 3 minutes!
I grabbed Crockford's json2.js and had to disable his check for existing
implementations. I've documented this here:
http://ossareh.posterous.com/how-to-patch-riak-0140-to-avoid-the-newline-p
Cheers,
mike
On Wed, Mar 23, 2011 at 13:34, Aphyr wro
Newline parsing is broken in JSON2.js shipped with Riak. Drop a more
recent version of JSON2.js in the directory referred to by js_source_dir
in app.config's riak_kv section, e.g.
{js_source_dir, "/etc/riak/js/"}
and reload the node.
--Kyle
On 03/23/2011 01:31 PM, Michael Ossareh wrote:
Gre
Greets,
https://gist.github.com/883872
That stack trace is the product of calling Riak.mapValuesJson in a map phase
of a map reduce job. I checked the same parsing against Chrome and Firefox
and they both parse the string as I'd expect. The object, as a string, that
is being parsed is:
"{\"bar\"
Great to get started on this work.
I'd like to see some examples of how this is used [I have one below]; I think
that would establish context for discussion. With just the raw API, one has to
envision how things interact, which is difficult.
From the client side, the moniker RiakObject is actu
Hi,
I'm trying to make the Java client easier to use and less tied to underlying
implementation so I've started designing a new API.
I've put some interfaces up at https://github.com/russelldb/riak-java-client-api
I'd really appreciate any comments you may have.
My intention is to adapt the ex
Hi,
I am running load tests with 7 Riak servers with Various Backend Storages.
1.
Whenever I start riak load test I get this Information
INFO: Est. data size: 30.52 GB
Actually in the folder data, its around 1.2 GB including all the nodes
in the cluster ?
- Even if i change the time for
19 matches
Mail list logo
