You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mesos.apache.org by "jiraposter@reviews.apache.org (JIRA)" <ji...@apache.org> on 2012/04/26 08:25:33 UTC
[jira] [Commented] (MESOS-145) mesos executor holds on to fd
spawned by slave after slave death, preventing slave from restarting
[ https://issues.apache.org/jira/browse/MESOS-145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13262405#comment-13262405 ]
jiraposter@reviews.apache.org commented on MESOS-145:
-----------------------------------------------------
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/4891/
-----------------------------------------------------------
Review request for mesos, Benjamin Hindman and John Sirois.
Summary
-------
This should fix MESOS-145
This addresses bug mesos-145.
https://issues.apache.org/jira/browse/mesos-145
Diffs
-----
third_party/libprocess/src/net.hpp 498e920
third_party/libprocess/src/process.cpp d77b156
Diff: https://reviews.apache.org/r/4891/diff
Testing
-------
make check (on mac)
Thanks,
Vinod
> mesos executor holds on to fd spawned by slave after slave death, preventing slave from restarting
> --------------------------------------------------------------------------------------------------
>
> Key: MESOS-145
> URL: https://issues.apache.org/jira/browse/MESOS-145
> Project: Mesos
> Issue Type: Bug
> Reporter: brian wickman
> Assignee: Benjamin Hindman
>
> The slaves spin on this error trying to start up as long as my (admittedly badly behaving) executor holds onto the handle the MesosDriver uses for communication with the slave:
> F0203 04:26:18.204121 580 process.cpp:1177] Failed to initialize, bind: Address already in use [98]
> *** Check failure stack trace: ***
> @ 0x7f258750db4d google::LogMessage::Fail()
> @ 0x7f25875137b7 google::LogMessage::SendToLog()
> @ 0x7f258750f3fc google::LogMessage::Flush()
> @ 0x7f258750f629 google::LogMessage::~LogMessage()
> @ 0x7f258750f72d google::ErrnoLogMessage::~ErrnoLogMessage()
> @ 0x7f258752517d process::initialize()
> @ 0x4067fa main
> @ 0x7f2585dae994 __libc_start_main
> @ 0x405c99 (unknown)
> Ben identified the root cause as needing to fcntl(F_SETFD) on the fd prior to fork.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira