reef-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shravan Matthur Narayanamurthy (JIRA)" <>
Subject [jira] [Commented] (REEF-1674) Random Failures in Broadcast and Reduce Fault Tolerance tests
Date Sat, 19 Nov 2016 02:15:58 GMT


Shravan Matthur Narayanamurthy commented on REEF-1674:

Thanks for pointing this out. I took a look at this. Two things that stand out: First it is
implemented as an event handler and it throws an exception. I am inside IMRU and don't have
control over binding event handlers. Also I want to be able to just exit instead of throwing
an exception. The redundancy in code is so small that I am inclined to just use what I have
now instead of getting PoisonedEventHandler to work. WDYT? Let me submit a PR and you can
tell me if there is a simple way to use PoisonedEventHandler.

> Random Failures in Broadcast and Reduce Fault Tolerance tests
> -------------------------------------------------------------
>                 Key: REEF-1674
>                 URL:
>             Project: REEF
>          Issue Type: Improvement
>          Components: REEF.NET IO
>    Affects Versions: 0.16
>            Reporter: Shravan Matthur Narayanamurthy
>            Assignee: Shravan Matthur Narayanamurthy
>            Priority: Minor
>             Fix For: 0.16
> The current fault tolerance tests inject simulated failure in a controlled manner and
hence are not the right failure model to test our fault tolerance work. It would be good to
have failures injected randomly than only at specific points as is done in the current code.

This message was sent by Atlassian JIRA

View raw message