[ofiwg] fault-tolerance

Jeff Hammond jeff.science at gmail.com
Tue Sep 8 10:40:46 PDT 2015

Some of the requirements for FT include:
- precise error code reporting on failures.  deadlock never occurs due to
remote process failure.
- containment of side effects of endpoint failures, especially no byzantine
- easy to deregister failed endpoints.
- easy to register new endpoints on the fly.  (think
MPI_Comm_spawn_multiple here)



On Tue, Sep 8, 2015 at 10:28 AM, Sur, Sayantan <sayantan.sur at intel.com>

> >
> >What would be more helpful would be to have OFI provide a well-specified
> >mechanism for reporting communication failures that it can’t
> >automatically resolve. Some sort of error reporting from OFI calls to say
> >that a specific send failed would be nice. From that error code, we can
> >infer which target failed since OFI doesn’t have any collectives which
> >would make this more difficult.
> Errors should be reported to the CQ readerr. That’s what you want, right?
> Thanks,
> Sayantan.
> >
> >Thanks,
> >Wesley
> >
> >
> >
> >On 9/8/15, 11:57 AM, "ofiwg-bounces at lists.openfabrics.org on behalf of
> >Hefty, Sean" <ofiwg-bounces at lists.openfabrics.org on behalf of
> >sean.hefty at intel.com> wrote:
> >
> >>> What's the state of fault-tolerance in OFI?  Would it be prudent for
> >>> someone to write OFI code that aspired to survive process failures?
> >>>Are
> >>> any implementations known to support this robustly right now?
> >>
> >>This would be provider specific.  I'm not aware of anything that's coded
> >>to handle failures.
> >>
> >>Having an example of this over libfabric would be great, though I'm not
> >>sure who's going to volunteer to write this.
> >>
> >>It's not clear to me how fault tolerance relates to a networking API.
> >>For example, what specific lower-level features does an app need to make
> >>this happen?  Are their restrictions that providers need to report to
> >>apps regarding their level of support?  Is this something that even
> >>belongs to this level of API?
> >>_______________________________________________
> >>ofiwg mailing list
> >>ofiwg at lists.openfabrics.org
> >>http://lists.openfabrics.org/mailman/listinfo/ofiwg
> >_______________________________________________
> >ofiwg mailing list
> >ofiwg at lists.openfabrics.org
> >http://lists.openfabrics.org/mailman/listinfo/ofiwg

Jeff Hammond
jeff.science at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openfabrics.org/pipermail/ofiwg/attachments/20150908/16fe3b6b/attachment.html>

More information about the ofiwg mailing list