mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron Bell (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MESOS-703) master fails to respect updated FrameworkInfo when the framework scheduler restarts
Date Tue, 03 Mar 2015 18:32:04 GMT

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

Aaron Bell commented on MESOS-703:
----------------------------------

Another major user impact discussed with Adam B: If you flip the checkpointing flag on any
framework, you need to restart masters and rolling restart all slaves.

> 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: 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)

Mime
View raw message