Mailing-List: contact mesos-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mesos-dev@incubator.apache.org
Date: Wed, 19 Oct 2011 01:45:10 +0000 (UTC)
From: "John Sirois (Commented) (JIRA)" <jira@apache.org>
To: mesos-dev@incubator.apache.org
Message-ID: 
 <1120783956.8863.1318988710726.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1268399358.8811.1318987150695.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (MESOS-40) CHECK failure in sched.cpp:467
 attempting to send framework message to slave, slave != UPID()
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/MESOS-40?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13130304#comment-13130304 ] 

John Sirois commented on MESOS-40:
----------------------------------

This is for mesos @ 32f48e9f04c7d9a65c5809c99e79e46a6db627b3: https://github.com/mesos/mesos/commit/32f48e9f04c7d9a65c5809c99e79e46a6db627b3


> CHECK failure in sched.cpp:467 attempting to send framework message to slave, slave != UPID() 
> ----------------------------------------------------------------------------------------------
>
>                 Key: MESOS-40
>                 URL: https://issues.apache.org/jira/browse/MESOS-40
>             Project: Mesos
>          Issue Type: Bug
>         Environment: Twitter java scheduler sending framework message via JNI interface.
>            Reporter: John Sirois
>
> I1019 00:51:19.701259 39888 coordinator.cpp:191] Coordinator attempting to write APPEND action at position 1519995
> I1019 00:51:19.701266 39888 coordinator.cpp:282] Coordinator attempting to commit APPEND action at position 1519995
> ...
> I1019 00:51:19.708601 39886 replica.cpp:818] Persisted action at 1519995
> I1019 00:51:19.708643 39886 sched.cpp:456] Asked to send framework message to slave 201110180211-0000001986-3529
> F1019 00:51:19.708667 39886 sched.cpp:467] Check failed: slave != UPID() 
> *** Check failure stack trace: ***
>     @     0x7f067f52e7bd  google::LogMessage::Fail()
>     @     0x7f067f534477  google::LogMessage::SendToLog()
>     @     0x7f067f530074  google::LogMessage::Flush()
>     @     0x7f067f5302d6  google::LogMessageFatal::~LogMessageFatal()
>     @     0x7f067f339fd2  mesos::internal::SchedulerProcess::sendFrameworkMessage()
>     @     0x7f067f325c8d  std::tr1::_Function_handler<>::_M_invoke()
>     @     0x7f067f32971e  std::tr1::_Function_handler<>::_M_invoke()
>     @     0x7f067f56e935  process::ProcessBase::serve()
> 2011-10-19 00:51:19,713:39852(0x48576940):ZOO_DEBUG@zookeeper_process@1974: Got ping response in 0 ms
>     @     0x7f067f331e75  ProtobufProcess<>::operator()()
>     @     0x7f067f575372  process::ProcessManager::run()
>     @     0x7f067f5754e0  process::trampoline()
>     @     0x7f068b39e870  (unknown)

--
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