You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mesos.apache.org by "Vinod Kone (JIRA)" <ji...@apache.org> on 2013/09/25 20:56:07 UTC
[jira] [Commented] (MESOS-703) master fails to respect updated
FrameworkInfo when the framework scheduler restarts
[ https://issues.apache.org/jira/browse/MESOS-703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13777916#comment-13777916 ]
Vinod Kone commented on MESOS-703:
----------------------------------
Updating FrameworkInfo is a feature that is not cleanly supported yet. We have plans to get to it before we release 1.0.
That said, the only current way to update FrameworkInfo is to restart the master and the slaves *after* you restart the framework with updated FrameworkInfo.
> master fails to respect updated FrameworkInfo when the framework scheduler restarts
> -----------------------------------------------------------------------------------
>
> Key: MESOS-703
> URL: https://issues.apache.org/jira/browse/MESOS-703
> Project: Mesos
> Issue Type: Bug
> Components: master
> Affects Versions: 0.14.0
> Environment: ubuntu 13.04, mesos 0.14.0-rc3
> Reporter: Jordan Curzon
>
> When I first ran marathon it was running as a personal user and registered with mesos-master as such due to putting an empty string in the user field. When I restarted marathon as "nobody", tasks were still being run as the personal user which didn't exist on the slaves. I know marathon was trying to send a FrameworkInfo with nobody listed as the user because I hard coded it in. The tasks wouldn't run as "nobody" until I restarted the mesos-master. Each time I restarted the marathon framework, it reregistered with mesos-master and mesos-master wrote to the logs that it detected a failover because the scheduler went away and then came back.
> I understand the scheduler failover, but shouldn't mesos-master respect an updated FrameworkInfo when the scheduler re-registers?
--
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