[
https://issues.apache.org/jira/browse/KAFKA-5775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colin P. McCabe resolved KAFKA-5775.
Resolution: Fixed
> Implement Fault Injection testing for Ka
://github.com/apache/kafka/pull/3726]
> Add ducktape integration for the Trogdor Fault injection daemon
> ---
>
> Key: KAFKA-5777
> URL: https://issues.apache.org/jira/browse/KAFKA-5777
>
Thanks, Victor. Also check out the fault injection umbrella JIRA here:
https://issues.apache.org/jira/browse/KAFKA-5775 with more subtasks.
cheers,
Colin
On Fri, Sep 1, 2017, at 05:07, Viktor Somogyi wrote:
> Hi Colin,
>
> I'd be interested in this and also think it's a val
a user-visible component, I think having a fault
> > injector will be really great for Kafka users. It will really help us
> > stress test Kafka in more situations. I'm going to post some patches in
> > a day or two-- it would be great to get some feedback. Check out
> > https://cwiki.apache.org/confluence/display/KAFKA/Fault+Injection
> >
> > best,
> > Colin
>
Github user asfgit closed the pull request at:
https://github.com/apache/kafka/pull/3699
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enab
://github.com/apache/kafka/pull/3699]
> Add the Trogdor fault injection daemon
> --
>
> Key: KAFKA-5776
> URL: https://issues.apache.org/jira/browse/KAFKA-5776
> Project: Kafka
>
Colin P. McCabe created KAFKA-5777:
--
Summary: Add ducktape integration for the Trogdor Fault injection
daemon
Key: KAFKA-5777
URL: https://issues.apache.org/jira/browse/KAFKA-5777
Project: Kafka
Colin P. McCabe created KAFKA-5776:
--
Summary: Add the Trogdor fault injection daemon
Key: KAFKA-5776
URL: https://issues.apache.org/jira/browse/KAFKA-5776
Project: Kafka
Issue Type
Colin P. McCabe created KAFKA-5775:
--
Summary: Implement Fault Injection testing for Kafka
Key: KAFKA-5775
URL: https://issues.apache.org/jira/browse/KAFKA-5775
Project: Kafka
Issue Type
o post some patches in
> a day or two-- it would be great to get some feedback. Check out
> https://cwiki.apache.org/confluence/display/KAFKA/Fault+Injection
>
> best,
> Colin
atches in
a day or two-- it would be great to get some feedback. Check out
https://cwiki.apache.org/confluence/display/KAFKA/Fault+Injection
best,
Colin
GitHub user cmccabe opened a pull request:
https://github.com/apache/kafka/pull/3699
Add the Trogdor fault injection daemon
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/cmccabe/kafka trogdor-review
Alternatively you can
YES!
One of my goal for the fault-injection in our system tests is that
whoever fixes the issue will also add tests to make sure it stays
fixed.
On Wed, Oct 5, 2016 at 11:33 AM, Tom Crayford wrote:
> I did some stuff like this recently with simple calls to `tc` (samples that
> I used w
interest and whether the specific
> framework is important to the community.
>
> On Tue, Oct 4, 2016 at 5:46 PM, Joel Koshy wrote:
> > Hi Gwen,
> >
> > I've also seen suggestions of using Jepsen for fault injection, but
> >> I'm not familiar with
PM, Joel Koshy wrote:
> Hi Gwen,
>
> I've also seen suggestions of using Jepsen for fault injection, but
>> I'm not familiar with this framework.
>>
>> What do you guys think? Write our own failure injection? or write
>> Kafka tests in Jepsen?
>>
for "small" failures (local failures on a single node, like socket
disconnection, disk read errors, out of memory etc) I've used byteman
before - http://byteman.jboss.org/
On Tue, Oct 4, 2016 at 5:46 PM, Joel Koshy wrote:
> Hi Gwen,
>
> I've also seen suggesti
Hi Gwen,
I've also seen suggestions of using Jepsen for fault injection, but
> I'm not familiar with this framework.
>
> What do you guys think? Write our own failure injection? or write
> Kafka tests in Jepsen?
>
This would definitely add a lot of value and save a
Hi Team Kafka,
I was thinking of enhancing our system tests with some fault
injections. You know, drop random packets, partition some nodes,
delete disks, maybe play with system clocks. Fun stuff :)
I was thinking of adding the fault injection to our system tests, so
if someone reports a failure
18 matches
Mail list logo
