On Tue, Jun 17, 2014 at 12:46 PM, István wrote:
>
>
> The entire dataset is idempotent and immutable, so there is not even a
> slightest chance that we are ending up with different values on
> different nodes for the same key in the same bucket. It seems that
> anti-entropy still finds problems:
>
Thanks Jordan,
Much appreciated!
I think we are good now, I deleted the AAE data and restarted the
service on one node and I am going to monitor the growth of the AAE
folder over time. See what happens.
Best regards,
Istvan
On Tue, Jun 17, 2014 at 10:48 AM, Jordan West wrote:
> On Tue, Jun 17,
On Tue, Jun 17, 2014 at 9:46 AM, István wrote:
> Is there any reason to let AAE running if we don't mutate the data in
> place?
>
Yes. If your data is infrequently accessed after being written then no
read-repair will take place. While values may not conflict, values may be
missing (e.g. a writ
Hi guys,
I just noticed looking at the disk utilization that AAE is consuming a
significant amount of space on the hard drive.
du -hs /var/lib/riak/*| grep anti
68G /var/lib/riak/anti_entropy
The entire dataset is idempotent and immutable, so there is not even a
slightest chance that we are
