[Apologies for crossposting]
Call for industrial and research papers for the 1st International Workshop on NoSQL Databases and Linked Data Applications (part of DEXA 2014 in Munich).
For industrial papers: We are looking for experience reports on NoSQL databases and linked open data in industria
> Date: Thu, 10 Apr 2014 14:42:23 +0100
> From: Guido Medina
> To: Engel Sanchez , Luke Bakken
> Cc: riak-users
> Subject: Re: Rebuilding AAE hashes - small question
> Message-ID: <53469fbf.1000...@temetra.com>
> Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
>
> Thanks Engel,
Hi,
Base on the documentation and tricks I have seen to fix/repair stuff in
Riak I would suggest the following approach:
riak-admin [cluster] (if cluster is specified then run the
action at every node)
and I know most of the commands are designed like that but adding to
them for speci
I have a 5-node cluster (riak 1.4.0, freebsd9) that is being used in
production and miscalculated the disk space being used by the cluster as
a whole. Yesterday I told the cluster to remove two nodes, leaving just
three, but I need four active to cover the usage.
One node left successfully be
Hi all,
Most of my data is in parent-child format (1:n).
For read/write performance, is it better to store parents in a separate bucket
and reference with IDs in children, or store complete copies of parents within
children?
Thanks,
Meghna
___
riak-u
How much deeper does your tree go? What's the average number of
children a node has? What is your query pattern (fetch a parent, and
all of its children?)?
On Fri, Apr 11, 2014 at 10:13 AM, Sapre, Meghna A
wrote:
> Hi all,
>
> Most of my data is in parent-child format (1:n).
>
> For read/write
Not any deeper. But a node can have a couple of thousand children in some
cases.
Query pattern is usually fetch all children for a parent.
Thanks,
Meghna
-Original Message-
From: Sargun Dhillon [mailto:sar...@sargun.me]
Sent: Friday, April 11, 2014 10:25 AM
To: Sapre, Meghna A
Cc: riak
Hi Guido,
Thanks a lot for the suggestions. I've passed them on internally.
--
Luke Bakken
CSE
lbak...@basho.com
On Fri, Apr 11, 2014 at 2:03 AM, Guido Medina wrote:
> Hi,
>
> Base on the documentation and tricks I have seen to fix/repair stuff in Riak
> I would suggest the following approach:
There is no background process to read all keys in the cluster in this
version of Riak. The Active Anti Entropy(AAE)feature added in future
versions odes precisely this. It notices any replicas that are out of sync
and forces read repair. If the manual repair procedure is not working you
might cons
