Love it! Ideas in addition what was already mentioned: * network deterioration in Cold Standby setups * OOM in TarMK setups (either on-heap or off-heap) * out of disc space in TarMK setups * out of disc space for persistent cache
On 07/03/16 09:30, "Chetan Mehrotra" <chetan.mehro...@gmail.com> wrote: >Cool stuff Tomek! This was something which was discussed in last >Oakathon so great to have a way to do resilience testing >programatically. Would give it a try >Chetan Mehrotra > > >On Mon, Mar 7, 2016 at 1:49 PM, Stefan Egli <stefane...@apache.org> wrote: >> Hi Tomek, >> >> Would also be interesting to see the effect on the leases and thus >> discovery-lite under high memory load and network problems. >> >> Cheers, >> Stefan >> >> On 04/03/16 11:13, "Tomek Rekawek" <reka...@adobe.com> wrote: >> >>>Hello, >>> >>>For some time I've worked on a little project called oak-resilience. It >>>aims to be a resilience testing framework for the Oak. It uses >>>virtualisation to run Java code in a controlled environment, that can be >>>spoilt in different ways, by: >>> >>>* resetting the machine, >>>* filling the JVM memory, >>>* filling the disk, >>>* breaking or deteriorating the network. >>> >>>I described currently supported features in the README file [1]. >>> >>>Now, once I have a hammer I'm looking for a nail. Could you share your >>>thoughts on areas/features in Oak which may benefit from being >>>systematically tested for the resilience in the way described above? >>> >>>Best regards, >>>Tomek >>> >>>[1] >>>https://github.com/trekawek/jackrabbit-oak/tree/resilience/oak-resilience >>> >>>-- >>>Tomek Rękawek | Adobe Research | www.adobe.com >>>reka...@adobe.com >>> >> >>
