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

Vinod Kone commented on MESOS-377:
----------------------------------

Aha. Sounds like the master's acknowledgments of the registration never made it 
to the slave? Also, I'm assuming the above snippet is a grep of the log and not 
the actual master log, because I would expect a "Adding slave..." after each of 
the above messages.

We have had reports of one-way communication not working (e.g slave->master OK 
but master->slave NOT OK) in ec2 before, and iirc, it was due to 
misconfiguration of the ip addresses (e.g. using private instead of public ip).

I would be surprised if it had anything to do with cgroups at all. Did this go 
away after you disabled cgroups!? If yes, can you re-enable it and let me know 
if this is repeatable?
                
> 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

Reply via email to