You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@mesos.apache.org by "Artem Harutyunyan (JIRA)" <ji...@apache.org> on 2016/02/01 21:19:41 UTC

[jira] [Updated] (MESOS-3871) Document libprocess message delivery semantics

     [ https://issues.apache.org/jira/browse/MESOS-3871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Artem Harutyunyan updated MESOS-3871:
-------------------------------------
    Sprint: Mesosphere Sprint 26, Mesosphere Sprint 27, Mesosphere Sprint 28  (was: Mesosphere Sprint 26, Mesosphere Sprint 27)

> Document libprocess message delivery semantics
> ----------------------------------------------
>
>                 Key: MESOS-3871
>                 URL: https://issues.apache.org/jira/browse/MESOS-3871
>             Project: Mesos
>          Issue Type: Documentation
>          Components: documentation, libprocess
>            Reporter: Neil Conway
>            Assignee: Benjamin Hindman
>            Priority: Minor
>              Labels: mesosphere
>
> What are the semantics of {{send()}} in libprocess? Specifically, does libprocess guarantee that messages will not be dropped, reordered, or duplicated? These are important properties to understand when building software on top of libprocess.
> Clearly message drops are allowed. Message reordering _appears_ to be allowed, although it should only happen in corner cases (see MESOS-3870). Duplicate message delivery probably can't happen.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)