You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mesos.apache.org by "Florian Leibert (flo) (JIRA)" <ji...@apache.org> on 2013/03/05 00:43:18 UTC

[jira] [Created] (MESOS-377) Tasks stuck in STAGING

Florian Leibert (flo) created MESOS-377:
-------------------------------------------

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