[
https://issues.apache.org/jira/browse/MESOS-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13592961#comment-13592961
]
Florian Leibert (flo) edited comment on MESOS-377 at 3/5/13 2:20 AM:
---------------------------------------------------------------------
This is the output from that slave around that time:
I0305 00:40:03.265849 16760 slave.cpp:832] Status update: task
ct:create_airbed_dump_table_reservation2s:1362444000000:0 of framework chronos
is now in state TASK_FINISHED
I0305 00:40:03.288791 16760 slave.cpp:729] Got acknowledgement of status update
for task ct:create_airbed_dump_table_reservation2s:1362444000000:0 of framework
chronos
I0305 00:40:25.949547 16757 slave.cpp:1162] Current disk usage 6.11%. Max
allowed age: 6.57days
I0305 00:41:25.952038 16757 slave.cpp:1162] Current disk usage 6.11%. Max
allowed age: 6.57days
I0305 00:42:25.954380 16757 slave.cpp:1162] Current disk usage 6.11%. Max
allowed age: 6.57days
I0305 00:43:25.956194 16764 slave.cpp:1162] Current disk usage 6.11%. Max
allowed age: 6.57days
I0305 00:44:25.957572 16760 slave.cpp:1162] Current disk usage 6.11%. Max
allowed age: 6.57days
I0305 00:45:25.959857 16762 slave.cpp:1162] Current disk usage 6.11%. Max
allowed age: 6.57days
I0305 00:46:25.961526 16764 slave.cpp:1162] Current disk usage 6.11%. Max
allowed age: 6.57days
I0305 00:47:25.963459 16761 slave.cpp:1162] Current disk usage 6.11%. Max
allowed age: 6.57days
I0305 00:48:25.964849 16757 slave.cpp:1162] Current disk usage 6.11%. Max
allowed age: 6.57days
I0305 00:49:25.966219 16759 slave.cpp:1162] Current disk usage 6.11%. Max
allowed age: 6.57days
I0305 00:50:14.419162 16763 slave.cpp:832] Status update: task
ct:db_export-airbed_reservation2s:1362443400000:0 of framework chronos is now
in state TASK_FINISHED
I0305 00:50:14.422466 16757 slave.cpp:729] Got acknowledgement of status update
for task ct:db_export-airbed_reservation2s:1362443400000:0 of framework chronos
I0305 00:50:25.967716 16763 slave.cpp:1162] Current disk usage 6.11%. Max
allowed age: 6.57days
I0305 00:51:25.969148 16761 slave.cpp:1162] Current disk usage 6.11%. Max
allowed age: 6.57days
I0305 00:52:25.969948 16761 slave.cpp:1162] Current disk usage 6.11%. Max
allowed age: 6.57days
I0305 00:53:25.971843 16761 slave.cpp:1162] Current disk usage 6.11%. Max
allowed age: 6.57days
was (Author: florianleibert):
This is the output from that slave:
I0305 00:40:03.265849 16760 slave.cpp:832] Status update: task
ct:create_airbed_dump_table_reservation2s:1362444000000:0 of framework chronos
is now in state TASK_FINISHED
I0305 00:40:03.288791 16760 slave.cpp:729] Got acknowledgement of status update
for task ct:create_airbed_dump_table_reservation2s:1362444000000:0 of framework
chronos
I0305 00:40:25.949547 16757 slave.cpp:1162] Current disk usage 6.11%. Max
allowed age: 6.57days
I0305 00:41:25.952038 16757 slave.cpp:1162] Current disk usage 6.11%. Max
allowed age: 6.57days
I0305 00:42:25.954380 16757 slave.cpp:1162] Current disk usage 6.11%. Max
allowed age: 6.57days
I0305 00:43:25.956194 16764 slave.cpp:1162] Current disk usage 6.11%. Max
allowed age: 6.57days
I0305 00:44:25.957572 16760 slave.cpp:1162] Current disk usage 6.11%. Max
allowed age: 6.57days
I0305 00:45:25.959857 16762 slave.cpp:1162] Current disk usage 6.11%. Max
allowed age: 6.57days
I0305 00:46:25.961526 16764 slave.cpp:1162] Current disk usage 6.11%. Max
allowed age: 6.57days
I0305 00:47:25.963459 16761 slave.cpp:1162] Current disk usage 6.11%. Max
allowed age: 6.57days
I0305 00:48:25.964849 16757 slave.cpp:1162] Current disk usage 6.11%. Max
allowed age: 6.57days
I0305 00:49:25.966219 16759 slave.cpp:1162] Current disk usage 6.11%. Max
allowed age: 6.57days
I0305 00:50:14.419162 16763 slave.cpp:832] Status update: task
ct:db_export-airbed_reservation2s:1362443400000:0 of framework chronos is now
in state TASK_FINISHED
I0305 00:50:14.422466 16757 slave.cpp:729] Got acknowledgement of status update
for task ct:db_export-airbed_reservation2s:1362443400000:0 of framework chronos
I0305 00:50:25.967716 16763 slave.cpp:1162] Current disk usage 6.11%. Max
allowed age: 6.57days
I0305 00:51:25.969148 16761 slave.cpp:1162] Current disk usage 6.11%. Max
allowed age: 6.57days
I0305 00:52:25.969948 16761 slave.cpp:1162] Current disk usage 6.11%. Max
allowed age: 6.57days
I0305 00:53:25.971843 16761 slave.cpp:1162] Current disk usage 6.11%. Max
allowed age: 6.57days
> 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
