Return-Path: X-Original-To: apmail-incubator-mesos-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-mesos-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C8AD9DD71 for ; Tue, 5 Mar 2013 06:11:14 +0000 (UTC) Received: (qmail 95142 invoked by uid 500); 5 Mar 2013 06:11:14 -0000 Delivered-To: apmail-incubator-mesos-dev-archive@incubator.apache.org Received: (qmail 94999 invoked by uid 500); 5 Mar 2013 06:11:14 -0000 Mailing-List: contact mesos-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: mesos-dev@incubator.apache.org Delivered-To: mailing list mesos-dev@incubator.apache.org Received: (qmail 94712 invoked by uid 99); 5 Mar 2013 06:11:13 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Mar 2013 06:11:13 +0000 Date: Tue, 5 Mar 2013 06:11:13 +0000 (UTC) From: "Benjamin Hindman (JIRA)" To: mesos-dev@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (MESOS-377) Tasks stuck in STAGING MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/MESOS-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13593103#comment-13593103 ] Benjamin Hindman commented on MESOS-377: ---------------------------------------- If you still have access to the logs, it would be great to see what the master decided to do when after it attempted to register the slave. Likewise, can you correlate that with slave logs? Was the slave constantly crashing (e.g., when it was trying to launch a task?), restarting, and trying to register? > Tasks stuck in STAGING > ---------------------- > > Key: MESOS-377 > URL: https://issues.apache.org/jira/browse/MESOS-377 > Project: Mesos > Issue Type: Bug > Reporter: Florian Leibert (flo) > Priority: Blocker > > GIT SHA: ac9fb5b0c713653140d853f6af29aaa3e3829476 > I see more and more tasks stuck in STAGING - they ran a long time ago but are missing the assignment of a slave. > Is this a known bug? > ct:update_s3_deployment:1362348902328:1 ChronosTask:update_s3_deployment FINISHED i-6282fa11 > ct:update_s3_deployment:1362348900000:0 ChronosTask:update_s3_deployment STAGING > ct:update_s3_deployment:1362348000000:0 ChronosTask:update_s3_deployment FINISHED i-6282fa11 > ct:update_s3_deployment:1362347101316:1 ChronosTask:update_s3_deployment FINISHED i-6282fa11 > ct:update_s3_deployment:1362347100000:0 ChronosTask:update_s3_deployment STAGING > ct:update_s3_deployment:1362346200000:0 ChronosTask:update_s3_deployment FINISHED i-6282fa11 > ct:update_s3_deployment:1362345300000:0 ChronosTask:update_s3_deployment FINISHED i-6282fa11 > ct:update_s3_deployment:1362344400000:0 ChronosTask:update_s3_deployment FINISHED i-6282fa11 > ct:update_s3_deployment:1362343500000:0 ChronosTask:update_s3_deployment FINISHED > ct:update_s3_deployment:1362342600000:0 ChronosTask:update_s3_deployment FINISHED i-04097277 > ct:update_s3_deployment:1362341700000:0 ChronosTask:update_s3_deployment FINISHED i-6282fa11 > ct:update_mobile_use:1362355210893:1 ChronosTask:update_mobile_use STAGING > ct:update_mobile_use:1362355208879:0 ChronosTask:update_mobile_use FAILED i-6282fa11 > ct:update_mobile_use:1362355204743:2 ChronosTask:update_mobile_use STAGING -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira