[
https://issues.apache.org/jira/browse/MESOS-703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14525388#comment-14525388
]
Joris Van Remoortere commented on MESOS-703:
--------------------------------------------
[~vinodkone]I can't find the buttons to remove it from closed sprints. This got
added to a sprint originally because we had a patch that completed all of it :s
After that it got broken down into smaller tasks, not all of which got posted.
I'll see if I can find someone with the powers to remove this.
> 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: Epic
> Components: master
> Affects Versions: 0.14.0
> Environment: ubuntu 13.04, mesos 0.14.0-rc3
> Reporter: Jordan Curzon
> Labels: gsoc, gsoc2015, mentor, mesosphere, twitter
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)
