Re: Agent with External Containerizer ignores mesos.internal.RunTaskMessage

Same problem with /help http://pastebin.com/2KUPDWv9 Of course when I use Mesos or Docker Containerizer it works well, but we need our custom LXC based containers that's why we need External Containerizer. Thanks for reply, Łukasz On 21 October 2015 at 15:38, haosdent wrote:

Re: Agent with External Containerizer ignores mesos.internal.RunTaskMessage

Could "curl -vv http://10.0.0.184:5051/help; success? On Wed, Oct 21, 2015 at 9:30 PM, Łukasz Adamczyk wrote: > Hello, > > Any ideas? Maybe someone can suggest me what I should check? IMHO > mesos-agent hangs, it accepts new TCP connections (port 5051), so service > is

Re: Agent with External Containerizer ignores mesos.internal.RunTaskMessage

seems could not found the implemention of your External Containerizer. -> seems could not found the implemention of your External Containerizer in email. On Wed, Oct 21, 2015 at 10:19 PM, haosdent wrote: > Sounds like your External Containerizer have problems and seems could

Re: Agent with External Containerizer ignores mesos.internal.RunTaskMessage

Saw this on master log around the time slave was receiving KillTaskMessage: hierarchical.hpp:1326] No resources available to allocate! -Jojy > On Oct 19, 2015, at 9:05 AM, Łukasz Adamczyk wrote: > > Hello, > > TL;DR; > > I have odd problem with Mesos Agent +

Re: Agent with External Containerizer ignores mesos.internal.RunTaskMessage

Hello, Any ideas? Maybe someone can suggest me what I should check? IMHO mesos-agent hangs, it accepts new TCP connections (port 5051), so service is still listening, but suddenly stopped sending HTTP responses: http://pastebin.com/QsyMft7j Regards, Łukasz On 19 October 2015 at 18:05, Łukasz

Re: Agent with External Containerizer ignores mesos.internal.RunTaskMessage

And is it possible for you to use MesosContainerizer or DockerContainerizer instead of ExternalContainerizer? On Wed, Oct 21, 2015 at 9:34 PM, haosdent wrote: > Could "curl -vv http://10.0.0.184:5051/help; success? > > On Wed, Oct 21, 2015 at 9:30 PM, Łukasz Adamczyk

Re: Agent with External Containerizer ignores mesos.internal.RunTaskMessage

> No resources available to allocate! I think this log should be a normal log because of GLOG_V=20 On Wed, Oct 21, 2015 at 10:52 PM, Jojy Varghese wrote: > Saw this on master log around the time slave was receiving KillTaskMessage: > > hierarchical.hpp:1326] No resources

Re: RFC: license headers interfere with doxygen documentation (MESOS-3581)

Please be aware that doxygen renders html differently than the middleman (templating engine that we use on mesos.apache.org). So before pushing changes please verify everything locally (https://github.com/apache/mesos/tree/master/support/site-docker. Cheers, Artem. On Wed, Oct 21, 2015 at 1:56

Re: Still Failing: apache/mesos#1269 (master - b74ed17)

+dominic Not sure who is the owner of this travis build for apache/mesos. Dominic? I would love for us to support one CI system (ASF), instead of having to learn 3. I see 3 different windows machines (Windows Server 2012, Windows Server 2008, Windows Server 2008 R2) in ASF CI. Does any of them

Re: Community Sync Interval

The result of this poll was: Bi-weekly: 12 Weekly: 10 So while pretty even, bi-weekly wins the vote. Let's proceed with bi-weekly community syncs and we can always reevaluate going forward. Thanks, MPark. On Sun, Oct 18, 2015 at 10:51 PM zhiwei wrote: > +1 bi-weekly > >

Re: Still Failing: apache/mesos#1269 (master - b74ed17)

>There is also the question of multiple people (hopefully all committers) having ownership access to the CI builds. Does Travis and Appveyor allow that? Travis allows this according my test just now. Appveyor doesn't allow so far. On Thu, Oct 22, 2015 at 3:35 AM, Vinod Kone

Re: Agent with External Containerizer ignores mesos.internal.RunTaskMessage

Sounds like your External Containerizer have problems and seems could not found the implemention of your External Containerizer. By the way, do you know External Containerizer is deprecated and we would let Containerizer become module. http://search-hadoop.com/m/0Vlr6yasmiJToni On Wed, Oct 21,

Re: minor doc fixes - do I need to have a JIRA ticket and a shepherd and a compass and a map of the pacific NW?

Hi Erik! For a simple patch like spelling / grammar mistakes you don't need a shepherd or a JIRA. Just submit your patch, and add a committer as a reviewer. If you don't have a relationship yet with one, you can add me (jvanremoortere), or in general just ask in IRC and someone will volunteer.

Re: minor doc fixes - do I need to have a JIRA ticket and a shepherd and a compass and a map of the pacific NW?

Thanks @Joris! I look forward to watching your (and Michael's) talk. - Erik On Wed, Oct 21, 2015 at 7:52 AM, Joris Van Remoortere wrote: > Hi Erik! > For a simple patch like spelling / grammar mistakes you don't need a > shepherd or a JIRA. > Just submit your patch, and

Newbie Guide (Mesos-3224)

Hi All, Below is the link to the Newbie Guide for review. It is in markdown format thus you may need to connect an app (e.g. SlackEdit) if you wish to make edits/comments. Your feedback is appreciated. Thanks! Doc: https://drive.google.com/file/d/0B9ZMdjw53LQocWo2YVNLdGF5a2M/view JIRA:

Re: RFC: license headers interfere with doxygen documentation (MESOS-3581)

Excellent idea! Let’s call this c) It’s more work than a), but has to be done eventually anyway. > On Oct 20, 2015, at 11:49 PM, Joseph Wu wrote: > > +/- 0 (a) wouldn't hurt, but isn't the best solution. > > > I'd vote for adding actual comment blocks to each class.

Re: RFC: license headers interfere with doxygen documentation (MESOS-3581)

Hi Joseph, yes, doing the right thing and having everything documented would make most of this cleaner. There is still an issue with e.g. namespaces (or anything else the particular language allows to be extended later on): {foo.hpp} /** Licensed .. */ /** Foo is

Can someone be the shepherd

Hi, I was working on JIRA #MESOS-3747 ( https://issues.apache.org/jira/browse/MESOS-3747), can someone be the sheperd? Thanks. Regards Liqiang Lin

Re: RFC: license headers interfere with doxygen documentation (MESOS-3581)

If this means that c) requires a), then we should do a) first, and then c) incrementally. > On Oct 21, 2015, at 10:23 AM, Benjamin Bannier > wrote: > > Hi Joseph, > > yes, doing the right thing and having everything documented would make most > of this