Re: WELCOME to user@mesos.apache.org
I am not sure this is the best place to ask for but I tried checking the IRC channel which seemed quite empty and didnt find anywhere else to ask general user questions/problems. But would appreciate some pointers and directions on how I can get it up. I also posted on the Jira ticket regarding this. I tried following the instructions set on here: http://mesosphere.io/learn/run-docker-on-mesosphere/ Instead of using a local machine (I am on osx), I setup a ubuntu 14 m3.large instance on my AWS acount then followed the instructions. I connected an elastic IP and a subdomain to the instance and opened all the ports on the firewall. However I am not getting any docker containers running. Here are my mesos and marathon urls: Marathon: mesos.cronycle.net:8080 Mesos: mesos.cronycle.net:5050 I just want to get a Rails application up on a docker container and be able to scale it automatically based on resource consumptions and also be able to use the procfile for it similar to Heroku. Is Mesos a good tool for this? I am currently looking at using Deis+CoreOS, but their statistics and monitoring tools seem to be non-existant, there's no automated way of monitoring processes like there is with marathon for instance. So would have liked to make it work ideally if possible. Thanks in advance. On Wed, Jul 9, 2014 at 2:02 PM, user-h...@mesos.apache.org wrote: Hi! This is the ezmlm program. I'm managing the user@mesos.apache.org mailing list. Acknowledgment: I have added the address nay...@cronycle.com to the user mailing list. Welcome to user@mesos.apache.org! Please save this message so that you know the address you are subscribed under, in case you later want to unsubscribe or change your subscription address. --- Administrative commands for the user list --- I can handle administrative requests automatically. Please do not send them to the list address! Instead, send your message to the correct command address: To subscribe to the list, send a message to: user-subscr...@mesos.apache.org To remove your address from the list, send a message to: user-unsubscr...@mesos.apache.org Send mail to the following for info and FAQ for this list: user-i...@mesos.apache.org user-...@mesos.apache.org Similar addresses exist for the digest list: user-digest-subscr...@mesos.apache.org user-digest-unsubscr...@mesos.apache.org To get messages 123 through 145 (a maximum of 100 per request), mail: user-get.123_...@mesos.apache.org To get an index with subject and author for messages 123-456 , mail: user-index.123_...@mesos.apache.org They are always returned as sets of 100, max 2000 per request, so you'll actually get 100-499. To receive all messages with the same subject as message 12345, send a short message to: user-thread.12...@mesos.apache.org The messages should contain one line or word of text to avoid being treated as sp@m, but I will ignore their content. Only the ADDRESS you send to is important. You can start a subscription for an alternate address, for example john@host.domain, just add a hyphen and your address (with '=' instead of '@') after the command word: user-subscribe-john=host.dom...@mesos.apache.org To stop subscription for this address, mail: user-unsubscribe-john=host.dom...@mesos.apache.org In both cases, I'll send a confirmation message to that address. When you receive it, simply reply to it to complete your subscription. If despite following these instructions, you do not get the desired results, please contact my owner at user-ow...@mesos.apache.org. Please be patient, my owner is a lot slower than I am ;-) --- Enclosed is a copy of the request I received. Return-Path: nay...@cronycle.com Received: (qmail 87716 invoked by uid 99); 9 Jul 2014 13:02:07 - Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Jul 2014 13:02:07 + X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [209.85.128.177] (HELO mail-ve0-f177.google.com) (209.85.128.177) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Jul 2014 13:02:03 + Received: by mail-ve0-f177.google.com with SMTP id i13so7054306veh.36 for user-sc.1404907934.jgmheaiblkgjbnadjlhc-nayeem= cronycle@mesos.apache.org; Wed, 09 Jul 2014 06:01:42 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=Ge1H6qrLizjA7gg328eGYMqtpwyBNglJfn4QZb71pYM=; b=LUVIt+M9mGLuwf91D7jnTyAIqRp6P+lF7Fe0ccDENFzmR17JSvzyG3lzVNMO/+b4Fj HBKgxnVA+N6+GOpCKhNSulqJuq9nyqIcRNdSDSthtA3QpXvq36WMvoYbMVNKG5hNj/hr
interested in organizing MUG
I am interested in organizing MUGs in London. Let me know how I can get started! :-)
Re: 0.19.1
I've added it to the 0.19.1 list since it's trivial and helps those using S3. On Fri, Jul 4, 2014 at 12:52 PM, Tom Arnfeld t...@duedil.com wrote: Happy to. It surprised me that this wasn't supported, especially considering the fetcher is supposed to be able to download URIs from any URL using http(s). This is most useful (and in my opinion quite an important issue) for downloading executors from S3 in situations a redirect is incurred, and more specifically, github tar archives which almost always go through a 301. Don't mind if going into the next non-bugfix release if you don't agree it's that important. On 4 Jul 2014, at 20:48, Dominic Hamon dha...@twopensource.com wrote: Hi Can you give some background as to why this is a critical fix? We try to minimise what we include in bug fix releases to avoid feature creep. Thanks On Jul 4, 2014 12:31 PM, Tom Arnfeld t...@duedil.com wrote: Any chance we can get https://issues.apache.org/jira/browse/MESOS-1448 too? On 3 Jul 2014, at 21:40, Vinod Kone vinodk...@gmail.com wrote: Hi, We are planning to release 0.19.1 (likely next week) which will be a bug fix release. Specifically, these are the fixes that we are planning to cherry pick. https://issues.apache.org/jira/issues/?filter=12326191jql=project%20%3D%20MESOS%20AND%20%22Target%20Version%2Fs%22%20%3D%200.19.1 If there are other critical fixes that need to be backported to 0.19.1 please reply here as soon as possible. Thanks,
Re: Mesos 19 startup error
I just tested that and I can't find any issues there. Was this on 0.19.0 where it crashes if non-existent, regardless of the trailing slash? On Sun, Jun 29, 2014 at 10:33 PM, Diptanu Choudhury dipta...@gmail.com wrote: Thanks Ben, by the way just noticed that on passing the trailing / to --work_dir the process crashes as well. For ex: --work_dir=/mnt/data/mesos/ On Fri, Jun 27, 2014 at 2:02 PM, Benjamin Mahler benjamin.mah...@gmail.com wrote: I created a ticket to track it for 0.19.1: https://issues.apache.org/jira/browse/MESOS-1551 On Fri, Jun 27, 2014 at 8:26 AM, Benjamin Hindman benjamin.hind...@gmail.com wrote: Yes, this was fixed in this commit https://github.com/apache/mesos/commit/1ce8d31fda545d69aea0637107f507c2b512adc9 . On Fri, Jun 27, 2014 at 8:25 AM, Diptanu Choudhury dipta...@gmail.com wrote: Thanks Ben! Indeed the directory isn't there. I thought mesos creates it on its own. Sent from my iPhone On 27 Jun 2014, at 08:18 am, Benjamin Hindman benjamin.hind...@gmail.com wrote: You need to create the --work_dir first (in your case '/tmp/work_dir') since the Mesos master doesn't create it automatically. Sorry about the error message, it looks much worse than it is! This has since been fixed and will be included in 0.19.1. Ben. On Fri, Jun 27, 2014 at 1:47 AM, Diptanu Choudhury dipta...@gmail.com wrote: Hi, When I start Mesos 0.19.0 on OSX 10.9, I get the following error - ./bin/mesos-master.sh --zk=zk://localhost:2181/mesos --work_dir=/tmp/work_dir/ --quorum=2 I0627 01:45:09.698272 1979613968 main.cpp:150] Build: 2014-06-27 01:03:13 by dchoudhury I0627 01:45:09.698837 1979613968 main.cpp:152] Version: 0.19.0 F0627 01:45:09.701522 1979613968 replica.cpp:721] CHECK_SOME(state): IO error: ~/work_dir/replicated_log/LOCK: No such file or directoryFailed to recover the log *** Check failure stack trace: *** @0x10cb0cdc4 google::LogMessage::SendToLog() @0x10cb0d2f3 google::LogMessage::Flush() @0x10cb1048f google::LogMessageFatal::~LogMessageFatal() @0x10cb0d9e9 google::LogMessageFatal::~LogMessageFatal() @0x10c535559 _CheckFatal::~_CheckFatal() @0x10c535429 _CheckFatal::~_CheckFatal() @0x10c9c3dba mesos::internal::log::ReplicaProcess::restore() @0x10c9c3861 mesos::internal::log::ReplicaProcess::ReplicaProcess() @0x10c9c6f9b mesos::internal::log::Replica::Replica() @0x10c93730a mesos::internal::log::LogProcess::LogProcess() @0x10c93cc80 mesos::internal::log::Log::Log() @0x10c93cbfd mesos::internal::log::Log::Log() @0x10c45180c main @ 0x7fff8b0465fd start Abort trap: 6 Any ideas, with what's going on here? I hope I am not invoking mesos-master incorrectly. -- Thanks, Diptanu Choudhury Web - www.linkedin.com/in/diptanu Twitter - @diptanu http://twitter.com/diptanu -- Thanks, Diptanu Choudhury Web - www.linkedin.com/in/diptanu Twitter - @diptanu http://twitter.com/diptanu
Python Celery on Mesos
Hey everyone, Posted this on IRC earlier but thought i'd bring it up here. Has anyone given any thought to building an extension to Celery (a popular python framework for building task based apps http://www.celeryproject.org/) to allow it to behave as a Mesos framework and run tasks on Mesos? I'm not very familiar with the internals of Celery so it might be more complex to achieve than it looks from the surface, but something we'd be interested in working with. Tom. -- Tom Arnfeld Developer // DueDil t...@duedil.com (+44) 7525940046 25 Christopher Street, London, EC2A 2BS Company Number: 06999618 What is DueDil? | Product features | Try it for free
Re: Python Celery on Mesos
You could run Celery through Marathon, you'd just also need to have a broker (Reddis, RabbitMQ) running concurrently on mesos (or elsewhere, technically) . Though it may be useful to framework the ability to package it all together. -Hunter On Wed, Jul 9, 2014 at 4:06 PM, Tom Arnfeld t...@duedil.com wrote: Hey everyone, Posted this on IRC earlier but thought i'd bring it up here. Has anyone given any thought to building an extension to Celery (a popular python framework for building task based apps http://www.celeryproject.org/) to allow it to behave as a Mesos framework and run tasks on Mesos? I'm not very familiar with the internals of Celery so it might be more complex to achieve than it looks from the surface, but something we'd be interested in working with. Tom. -- *Tom Arnfeld* Developer // DueDil t...@duedil.com (+44) 7525940046 25 Christopher Street, London, EC2A 2BS Company Number: 06999618 What is DueDil? https://www.duedil.com/about | Product features https://www.duedil.com/features?ref=ft | Try it for free https://www.duedil.com/
