> We need something different from the chaos monkeys. in this case we're not trying to peturb the cluster in ways we think it should handle; we're setting up a state we already know requires an outside tool.
Not sure this really falls outside the framework. Add an action that invokes hbck. Then, add a policy that schedules the hbck invocation as part of the schedule. That policy would also include the destructive actions breaking things in a way the tool needs to fix (or HBase can handle intrinsically...) On Tue, Oct 1, 2019 at 2:11 AM Sean Busbey <[email protected]> wrote: > I was chatting with Sakthi about automating some testing of hbck2 commands. > Nothing too fancy, I just want some assurance that they ought to work. > > This got us talking about how we might purposefully break a cluster to meet > a set of symptoms that hbck2 knows how to correct. We need something > different from the chaos monkeys. in this case we're not trying to peturb > the cluster in ways we think it should handle; we're setting up a state we > already know requires an outside tool. > > Where should this kind of tooling live? Main repo next to the monkeys? > Alongside hbck2 in operator tools? Somewhere else entirely? > -- Best regards, Andrew Words like orphans lost among the crosstalk, meaning torn from truth's decrepit hands - A23, Crosstalk
