[
https://issues.apache.org/jira/browse/MESOS-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13592982#comment-13592982
]
Florian Leibert (flo) commented on MESOS-377:
---------------------------------------------
Sorry for the confusion - the one timestamp you see that's off in chronos is
actually from when the task was originally launched. It was retried at a later
time - unfortunately, some of these systems have a relatively short log
history.
One thing that is weird is that this slave (the one running cgroups), was
constantly re-registering.
lt-mesos-master.INFO:I0304 17:34:44.536988 24440 master.cpp:924] Attempting to
register slave on i-d40e75a7 at slave(1)@10.108.205.116:5051
lt-mesos-master.INFO:I0304 17:49:43.657681 24444 master.cpp:924] Attempting to
register slave on i-d40e75a7 at slave(1)@10.108.205.116:5051
lt-mesos-master.INFO:I0304 18:10:06.125493 24441 master.cpp:924] Attempting to
register slave on i-d40e75a7 at slave(1)@10.108.205.116:5051
lt-mesos-master.INFO:I0304 18:19:46.478036 24441 master.cpp:924] Attempting to
register slave on i-d40e75a7 at slave(1)@10.108.205.116:5051
lt-mesos-master.INFO:I0304 18:25:30.404621 24440 master.cpp:924] Attempting to
register slave on i-d40e75a7 at slave(1)@10.108.205.116:5051
lt-mesos-master.INFO:I0304 18:31:56.071737 24446 master.cpp:924] Attempting to
register slave on i-d40e75a7 at slave(1)@10.108.205.116:5051
lt-mesos-master.INFO:I0304 20:30:09.107945 24442 master.cpp:924] Attempting to
register slave on i-d40e75a7 at slave(1)@10.108.205.116:5051
lt-mesos-master.INFO:I0304 21:04:43.982234 24445 master.cpp:924] Attempting to
register slave on i-d40e75a7 at slave(1)@10.108.205.116:5051
lt-mesos-master.INFO:I0304 22:55:30.878238 24447 master.cpp:924] Attempting to
register slave on i-d40e75a7 at slave(1)@10.108.205.116:5051
lt-mesos-master.INFO:I0304 23:10:31.753471 24446 master.cpp:924] Attempting to
register slave on i-d40e75a7 at slave(1)@10.108.205.116:5051
lt-mesos-master.INFO:I0304 23:44:26.337231 24445 master.cpp:924] Attempting to
register slave on i-d40e75a7 at slave(1)@10.108.205.116:5051
As mentioned above, I have now turned off cgroups on this slave.
> 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
