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
Toby,
While there is mention of it on the riak-admin page [1], in the upcoming
2.0 release `riak-admin backup` has been deprecated. The documentation you
linked contains the suggested ways for backing up your cluster at this
time. There are many ongoing discussions about providing a first-class
ba
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
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,
Hi all,
I am trying to set the Erlang scheduler bind type to nnts by adding the
following to vm.args:
+stbt nnts
In theory stbt is supposed to handle lack of support properly, but instead
my server fails to start. However it starts with just +sbt nnts.
Here is the Erlang doc on the flag: http:/
Hi Alain,
You're likely running an erlang version that's too early. +sbt was
added earlier than +stbt. They're otherwise equivalent, so using +sbt
should be OK.
On Tue, Jun 17, 2014 at 4:16 PM, Alain Rodriguez wrote:
> Hi all,
>
> I am trying to set the Erlang scheduler bind type to nnts by ad
