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

Posted to issues@mesos.apache.org by "Yong Tang (JIRA)" <ji...@apache.org> on 2016/03/25 23:53:25 UTC

[jira] [Updated] (MESOS-4601) Don't dump stack trace on failure to bind()

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

Yong Tang updated MESOS-4601:
-----------------------------
    Assignee:     (was: Yong Tang)

> Don't dump stack trace on failure to bind()
> -------------------------------------------
>
>                 Key: MESOS-4601
>                 URL: https://issues.apache.org/jira/browse/MESOS-4601
>             Project: Mesos
>          Issue Type: Bug
>          Components: libprocess
>            Reporter: Neil Conway
>              Labels: errorhandling, libprocess, mesosphere, newbie
>
> We should do {{EXIT(EXIT_FAILURE)}} rather than {{LOG(FATAL)}}, both for this code path and a few other expected error conditions in libprocess network initialization.



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