Hi Dave,

Thanks for the info. A few follow up questions:

* How much total data is in the cluster?
* Have you changed the AAE default settings at all? If so, to what?
* How much space was allocated for the AAE FS?

>
I was not expecting that AAE issues would be able to kill Riak.
>

So, we've never seen this before in testing, but, admittedly, we never
tested the case where AAE wasn't given enough disk space. While it's a
sub-optimal behavior, it's no different than Riak (or any other db daemon)
running out of storage space and dying. That said, the docs are *very*
sparse on AAE, and we only lay out the config defaults as part of the KV
section in the app.config file [0]. At the very least we should have the
expected systems needs for AAE storage documented. There's probably a
middle-ground mitigated with documentation in the short term. We're trying
to freeze for 1.4 at the moment, but I'll make sure this gets some
discussion time after that's done.

Mark

[0] http://docs.basho.com/riak/latest/references/Configuration-Files/



On Mon, May 27, 2013 at 10:22 AM, Dave Brady <[email protected]> wrote:

> Greetings,
>
> Some background: I have been testing using AAE in our backup ring.  I did
> not want the AAE data to sit on our (expensive and comparatively limited)
> SSD disks, so I created a LV for it on the systems' SAS disks.
>
> All seemed well for a few weeks.
>
> I got to doing other stuff for a bit, and when I came back to this ring
> today, I noticed that the filesystem used by AAE was full on all nodes.  I
> then noticed that Riak had crashed on every node because this problem.
>
> I was not expecting that AAE issues would be able to kill Riak.
>
> Anyone else had this happen?
> --
> Dave Brady
>
> _______________________________________________
> riak-users mailing list
> [email protected]
> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
>
>
_______________________________________________
riak-users mailing list
[email protected]
http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com

Reply via email to