Mesos agents across a WAN?

Given regional bare metal Mesos clusters on multiple continents, are there any known issues running some of the agents over the WAN? Is anyone else doing it, or is this a terrible idea that I should tell management no on? A few specifics: 1. Are there any known limitations or configuration

Re: Cleaning up failed tasks in the UI

I suspect that after your maintenance operation, Marathon may have registered with a new frameworkId and launched is own copies of your tasks (why you see double). However, the old Marathon frameworkId probably has a failover_timeout of a week, so it will continue to be considered "registered",

Re: Agent won't start

Hello Paul, Few things to note here: 1. Whenever, you change value of any *resource *or any *attribute* (Description: http://mesos.apache.org/documentation/latest/attributes-resources/), you need to cleanup the work_dir (rm -rf /tmp/mesos) and restart the slave. 2. You muse be already knowing

Re: Agent won't start

Greg, thanks again - I am planning on moving my work_dir. Pradeep, thanks again. In a slightly different scenario, namely, service mesos-slave stop edit /etc/default/mesos-slave (add a port resource) service mesos-slave start I noticed that slave did not start and - again - the log shows

Re: Compute event at Twitter HQ - 03/31

Hello everyone, The talks will indeed be recorded and made available on Twitter's YouTube channel. I will send an update after the event when the videos have been uploaded. Ian On Wed, Mar 16, 2016 at 6:16 PM, Micheal Benedict Arul wrote: > We won't be streaming

Re: MUG in Raleigh/Durham

Do you mean add your user group to http://mesos.apache.org/community/user-groups/ ? You could submit a pull request to https://github.com/apache/mesos/blob/master/site/source/community/user-groups.html.md and contact a committer help you submit it. On Wed, Mar 30, 2016 at 7:31 PM, John Crawford

Re: Cleaning up failed tasks in the UI

Hi haosdent, thanks for your reply. It is actually very weird, first time I see this situation in around one year using mesos. I am pasting here the truncate output you asked for. It is showing one of the tasks with "Failed" state under "Active tasks": { "executor_id":

MUG in Raleigh/Durham

Hello! I hosted a Meetup last night around Mesos and would like to know how we can become an "official" user group? Here is the link to the Meetup group I created: http://www.meetup.com/Triangle-Area-Mesos-User-Group/ Thanks! -- John Crawford Co-founder & CTO 733 Foster Street l Suite 500

Re: Cleaning up failed tasks in the UI

>"Active tasks" with status "Failed" A bit wired here. According to my test, it should exists in "Completed Tasks". If possible, could you show you /master/state endpoint result. I think the frameworks node in state response would be helpful to analyze the problem. On Wed, Mar 30, 2016 at 6:26

Cleaning up failed tasks in the UI

Hi all, after a maintenance carried on in a mesos cluster (0.25) using marathon (0.10) as a only scheduler , I've finished with the double of tasks for each application. But marathon was recognizing only half of them. For getting rid of this orphaned tasks, I've did a "kill PID" of them, so