You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mesos.apache.org by "Vinod Kone (JIRA)" <ji...@apache.org> on 2014/01/02 23:49:51 UTC
[jira] [Updated] (MESOS-889) Bad 'master' string given by scheduler
should not print a stack trace
[ https://issues.apache.org/jira/browse/MESOS-889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vinod Kone updated MESOS-889:
-----------------------------
Fix Version/s: 0.16.0
> Bad 'master' string given by scheduler should not print a stack trace
> ---------------------------------------------------------------------
>
> Key: MESOS-889
> URL: https://issues.apache.org/jira/browse/MESOS-889
> Project: Mesos
> Issue Type: Bug
> Reporter: Vinod Kone
> Assignee: Yan Xu
> Fix For: 0.16.0
>
>
> [vinod@smfd-atr-11-sr1 build]$ ./src/long-lived-framework 127.0.0.1
> F0102 22:12:42.508031 27439 sched.cpp:1245] Check failed: process != NULL
> *** Check failure stack trace: ***
> @ 0x7fed62b71bad google::LogMessage::Fail()
> @ 0x7fed62b75b97 google::LogMessage::SendToLog()
> @ 0x7fed62b74494 google::LogMessage::Flush()
> @ 0x7fed62b746c6 google::LogMessageFatal::~LogMessageFatal()
> @ 0x7fed6259529f mesos::MesosSchedulerDriver::stop()
> @ 0x4086cf main
> @ 0x7fed5ff089c4 __libc_start_main
> @ 0x407c69 (unknown)
> Aborted
> It would be nice to print a "unable to parse..." message like we do in master/slave than a stack trace here.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)