You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Guangya Liu (JIRA)" <ji...@apache.org> on 2015/08/31 12:11:45 UTC

[jira] [Assigned] (MESOS-1826) Improve logging for when master cannot connect to slaves

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

Guangya Liu reassigned MESOS-1826:
----------------------------------

    Assignee: Guangya Liu

> Improve logging for when master cannot connect to slaves
> --------------------------------------------------------
>
>                 Key: MESOS-1826
>                 URL: https://issues.apache.org/jira/browse/MESOS-1826
>             Project: Mesos
>          Issue Type: Improvement
>    Affects Versions: 0.20.0
>            Reporter: Thomas Rampelberg
>            Assignee: Guangya Liu
>            Priority: Minor
>              Labels: newbie
>
> When first setting a mesos cluster up, it is possible to get into a state where your slaves are constantly re-registering. This happens because the slave pid is not reachable from the master.
> Currently, the master logs make it pretty tough to figure out that this is the problem that is occurring. It would be fantastic if there was a better explanation in the logs, something like:
>     Unable to connect to slave X at x.x.x.x:5051. Please make sure that host is reachable from your master.



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