Ingo,
I have two guesses that might explain the symptoms:
- there is a bad drive in one the nodes, or
- one or more nodes begins to use swap space during a compaction or 2i
iteration.
I might be able to describe / isolate the problem by examining the "LOG" files
produced by leveldb. Wou
One practical matter to also keep in mind is the number of nodes you must scale
to and by.
The recommended minimum nodes when running Riak in production is five servers.
Once you start with that minimum, scaling is a matter of adding single nodes as
you need them, six to seven to eight and so o
Hey Norman,
On Mon, Mar 25, 2013 at 8:43 AM, Norman Khine wrote:
> hello,
> would you have any cost comparison analysis document which looks at a
> running a riak cluster versus mongodb sharded cluster, i am asking as
> i have been tasked to compare the cost of infrastructure when the
> volume o
We are looking to deploy a Riak cluster of 5 machines using the Bitcask
backend. We're storing almost all user-specific data in Riak, as well as
session data which will be validated on each request.
Generally speaking, each API request will result in either 4-5 writes to
Riak or 4-5 reads from Ria
Hi:
This is my code[1]. The error log is [2] and[3].
May be this is * [{<<"}~\bgQU&\331">>*,{1,63531874791}}] cause error. I am
not sure.
Please give some idea. Thanks all.
Jason
[1]
62 map(Record, undefined, {get_bucket_and_key, Bucket, Key}) ->
63 ?DEBUG("~p:map ~p Record=~p~n", [?MODULE
