Re: Finding Tasks Waiting for Resources in Mesos

I think you need to query the framework that you are running on top of Mesos for this information. The workflow is as follows: User submits a task to framework, framework waits for resources to be available in Mesos cluster, once available it launches the task. On Tue, Oct 31, 2017 at 11:16 AM,

Re: orphan executor

Can you share the agent and executor logs of an example orphaned executor? That would help us diagnose the issue. On Fri, Oct 27, 2017 at 8:19 PM, Mohit Jaggi wrote: > Folks, > Often I see some orphaned executors in my cluster. These are cases where > the framework was

Disallowing comma in attribute values

Hi folks, I would like to propose that we enforce the character set used for attribute values as per the documentation. Currently, the documentation states that attribute values should be of the form [a-zA-Z0-9_/.-] but we

Re: Adding the limited resource to TaskStatus messages

> In the case that a task is killed because it violated a resource > constraint (ie. the reason field is REASON_CONTAINER_LIMITATION, > REASON_CONTAINER_LIMITATION_DISK or REASON_CONTAINER_LIMITATION_MEMORY), > this field may be populated with the resource that triggered the > limitation. This is

Re: Collect feedbacks on TASK_FINISHED

I think it makes sense for `TASK_KILLED` to be sent in response to a KILL call irrespective of the exit status. IIRC, that was the original intention. On Thu, Sep 21, 2017 at 8:20 PM, Qian Zhang wrote: > Hi Folks, > > I'd like to collect the feedbacks on the task state

Re: [ISSUE] Check failed: slave.maintenance.isSome()

This looks similar to https://issues.apache.org/jira/browse/MESOS-7966. Can you add your information and logs to that ticket? On Fri, Sep 15, 2017 at 3:18 AM, Qi Feng wrote: > My mesos version is 1.2.0. Sorry. > > -- > *From:* Qi Feng

Re: [VOTE] Release Apache Mesos 1.4.0 (rc5)

ps://issues.apache.org/jira/browse/MESOS-6345> related > to persistent volume framework, which leads me to believe that this is not > new. > > Thanks, > > MPark > > On Tue, Sep 12, 2017 at 12:01 PM Vinod Kone <vinodk...@apache.org> wrote: > >> Tested this on

Re: [VOTE] Release Apache Mesos 1.4.0 (rc5)

Tested this on ASF CI. Saw 3 flaky tests. https://issues.apache.org/jira/browse/MESOS-7729 https://issues.apache.org/jira/browse/MESOS-7971 https://issues.apache.org/jira/browse/MESOS-7972 The first one was a known (since 1.4.0) flaky test

Re: SchedulerDriver / libmesos API version compatibility

Scheduler APIs, will this be > compatible with a 1.3.0 mesos master? > Or, do I need to upgrade to the v1 scheduler API in order to be compatible? > >> On 8 Sep 2017, at 10:41 am, Vinod Kone <vinodk...@gmail.com> wrote: >> >> Could be. We don't guarantee backwards compat

Re: SchedulerDriver / libmesos API version compatibility

Could be. We don't guarantee backwards compatible between pre 1.0 components and post 1.0 components. Component here could be master/agent binaries, scheduler/executor libs and jars and eggs. @vinodkone > On Sep 7, 2017, at 3:25 PM, Eli Jordan wrote: > > Hi > > Is

Re: Welcome James Peach as a new committer and PMC memeber!

Congrats and welcome! On Wed, Sep 6, 2017 at 2:22 PM, Jie Yu wrote: > Congrats James! Well deserved! > > On Wed, Sep 6, 2017 at 2:08 PM, Yan Xu wrote: > >> Hi Mesos devs and users, >> >> Please welcome James Peach as a new Apache Mesos committer and PMC

Re: [VOTE] Release Apache Mesos 1.1.3 (rc2)

+1 (binding) Tested on ASF CI. The only red build was the known perf core dump issue. *Revision*: ce77d91bd3a59227d5684ce0783b460c54ea311f - refs/tags/1.1.3-rc2 Configuration Matrix gcc clang centos:7 --verbose --enable-libevent --enable-ssl autotools [image: Success]

Re: [VOTE] Release Apache Mesos 1.4.0 (rc1)

Ran on ASF CI. Found 3 issues with tests. 1) GarbageCollectorIntegrationTest.ExitedFramework : This one seems fairly new. *@Kapil can you confirm if this is a test issue or something in the code?* 2) DiskResource Persistent Volume tests seem to

Re: [VOTE] Release Apache Mesos 1.3.1 (rc1)

+1 (binding) Tested on ASF CI. The 2 red builds are known flaky tests (health checks) and a perf core dump issue that's fixed on HEAD. *Revision*: 1beaede8c13f0832d4921121da34f924deec8950 - refs/tags/1.3.1-rc1 Configuration Matrix gcc clang centos:7 --verbose --enable-libevent --enable-ssl

Re: Containerizers & Executors

See my answers inline. > 1. Mesos Containerizer > - posix isolators > - cgroups isolators > Mesos container also allows you to use custom isolators. > 2. Docker containerizer > - docker isolators > Docker containerizer doesn't have a concept of isolator(s).

Re: dynamic resource reservations

Typically a framework with no role cannot use resources reserved for another role. So, it would be interesting to see what happened. Also, please be aware that directly upgrading from 0.28.0 to 1.3.0 is not supported. You need to go from 0.28.0 to 1.0.0 and then jump from 1.0.0 to 1.3.0. On Fri,

Re: How to detemine Mesos Capabilities?

When a scheduler registers or re-registers with the master, `MasterInfo` is provided as the callback. This includes the version information which can be used to determine which capabilities a Master has. This is admittedly not great; there is a ticket to introduce Master capabilities and include

Re: Agent Working Directory Best Practices

This is great information. Thanks for sharing Steven! On Tue, Jun 27, 2017 at 7:05 AM, Steven Schlansker < sschlans...@opentable.com> wrote: > > > On Jun 25, 2017, at 11:24 PM, Benjamin Mahler > wrote: > > > > As a data point, as far as I'm aware, most users are using a

Re: Work group on Community

> others. > > All the best! > Judith > > >> On Wed, Jun 21, 2017 at 2:47 AM, Jörg Schad <jo...@mesosphere.io> wrote: >> Very excited and happy to join! >> >>> On Sat, Jun 17, 2017 at 1:38 AM, James Peach <jor...@gmail.com> wrote: >&g

Re: Docker support bug in Mesos Containerizer in 1.3.0

There is. It's monthly unless it's urgent, in which case it could be done on demand. @vinodkone > On Jun 21, 2017, at 8:10 AM, Michael Park wrote: > > We have not set a 1.3.1 just yet. I'd be in charge of making that happen > though. > I'm happy to cut one, I'm not sure if

Re: On Apache Mesos release process

Thanks for starting the discussion around on this Alex! Much appreciated and needed. I agree with all the points here :) I'm a big proponent of predictable time based releases. As an aside, should we spin up a working group for releases? Given the frequency of our releases and burn down meetings

Welcome Greg Mann as a new committer and PMC member!

Hi folks, Please welcome Greg Mann as the newest committer and PMC member of the Apache Mesos project. Greg has been an active contributor to the Mesos project for close to 2 years now and has made many solid contributions. His biggest source code contribution to the project has been around

Re: What is the scheduler for the Command Executor

Hey Wenzhao. Sorry for the delay in response to your earlier email. Looks like this email is a duplicate of that, so I'll just answer this one. Please feel free to ask further questions on this email thread. I'm studying Mesos code, become very confused about the internal working > flow of

Re: RFC: Partition Awareness

On Thu, Jun 1, 2017 at 2:22 PM, Benjamin Mahler wrote: > If I understood correctly, the proposal is to not kill the tasks for > non-partition aware frameworks? That seems like a pretty big change for > frameworks that are not partition aware and expect the old killing >

Re: [VOTE] Release Apache Mesos 1.3.0 (rc3)

Thanks for the triage. +1 (binding) On Wed, May 31, 2017 at 1:33 PM, Neil Conway wrote: > On Tue, May 30, 2017 at 3:43 PM, Neil Conway > wrote: > > Attached is the test log for this failure. From a quick look, seems as > > though the agent starts

Re: [Req]Starting Japan User Group

Great to hear about the participation for the meetup! On Tue, May 30, 2017 at 9:22 PM, Kitayama, Shingo wrote: > When you are interested, please register it from followings!! > > Slack: https://mesostokyo.slack.com/ > > Slack Registration:

Re: [VOTE] Release Apache Mesos 1.3.0 (rc3)

Ran on ASF CI. Found following issues. Failed test: CommandExecutorCheckTest.CommandCheckDeliveredAndReconciled

Re: [RESULT][VOTE] Release Apache Mesos 1.0.4 (rc2)

We are officially done with 1.0.x. @vinodkone > On May 25, 2017, at 8:55 PM, Benjamin Mahler <bmah...@apache.org> wrote: > > Should we add a 1.0.5 release version to JIRA? Or are we done with 1.0 bug > fix release support? > >> On Thu, May 4, 2017 at 12:32 PM, Vinod

Re: Welcome Gilbert Song as a new committer and PMC member!

Congrats Gilbert! On Wed, May 24, 2017 at 1:32 PM, Neil Conway wrote: > Congratulations Gilbert! Well-deserved! > > Neil > > On Wed, May 24, 2017 at 10:32 AM, Jie Yu wrote: > > Hi folks, > > > > I' happy to announce that the PMC has voted Gilbert

Re: Use of ACLs.RegisterAgent.agent

If it hasn't been released it should be ok for us to do the rename. There are no backwards compatible guarantees for such things. But a heads up is always nice, so thanks for doing that. On Wed, May 24, 2017 at 12:44 PM, Neil Conway wrote: > FYI, I merged the change to

Re: [VOTE] Release Apache Mesos 1.2.1 (rc1)

Ran it on ASF CI and saw some issues. Segfault in "MasterTest.MultipleExecutors" in two builds [1]

Re: [VOTE] Release Apache Mesos 1.1.2 (rc2)

+1 (binding) Ran on ASF CI. The one configuration that is in "red" is due to a known flaky issue with perf core dump during test suite teardown. *Revision*: 37d98c55e1f43d6734729b5cdbed242ebc3263ed - refs/tags/1.1.2-rc2 Configuration Matrix gcc clang centos:7 --verbose --enable-libevent

Re: [Req]Starting Japan User Group

On Tue, May 9, 2017 at 8:10 AM, Kitayama, Shingo wrote: > In Japan, usually engineers will take tech event information from > CONNPASS, not from Meetup.com > > ※CONNPASS https://connpass.com/ (Sorry all Japanese) > > > > I think using whatever portal works for you is

Re: [VOTE] Release Apache Mesos 1.1.2 (rc1)

I saw this on ASF CI

[RESULT][VOTE] Release Apache Mesos 1.0.4 (rc2)

Hi all, The vote for Mesos 1.0.4 (rc2) has passed with the following votes. +1 (Binding) -- Ben Mahler Vinod Kone Anand Mazumdar +1 (Non-binding) -- There were no 0 or -1 votes. Please find the release at: https

Re: [VOTE] Release Apache Mesos 1.0.4 (rc2)

%3A14.04,label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/> [image: Success] <https://builds.apache.org/view/M-R/view/Mesos/job/Mesos-Release/32/BUILDTOOL=cmake,COMPILER=clang,CONFIGURATION=--verbose,ENVIRONMENT=GLOG_v=1%20MESOS_VERBOSE=1,OS=ubuntu%3A14.04,la

[VOTE] Release Apache Mesos 1.0.4 (rc2)

Hi all, Please vote on releasing the following candidate as Apache Mesos 1.0.4. 1.0.4 includes the following: * [MESOS-2537] - AC_ARG_ENABLED checks are broken * [MESOS-6606] - Reject optimized builds

Re: [VOTE] Release Apache Mesos 1.0.4 (rc1)

che.org/jira/browse/MESOS-6360 > > Also successfully ran the `test-upgrade.py` script both from 0.28.3 -> > 1.0.4-rc1 and from 1.0.4-rc1 -> 1.1.1 > > Cheers, > Greg > > > On Mon, Apr 24, 2017 at 3:23 PM, Vinod Kone <vinodk...@apache.org

Fwd: Github's disappearing mirrors

FYI -- Forwarded message -- From: Chris Lambertus Date: Fri, Apr 28, 2017 at 12:22 PM Subject: Github's disappearing mirrors To: committers Hello committers, We have received quite a few reports of github mirrors gone missing. We’ve

Re: [VOTE] Release Apache Mesos 1.0.4 (rc1)

buntu%3A14.04,label_exp=(docker%7C%7CHadoop)&&(!ubuntu-us1)&&(!ubuntu-eu2)/> On Mon, Apr 17, 2017 at 4:49 PM, Adam Bordelon <a...@mesosphere.io> wrote: > -0, wish we could include the fix for https://issues.apache.org/jira &

[VOTE] Release Apache Mesos 1.0.4 (rc1)

Hi all, Please vote on releasing the following candidate as Apache Mesos 1.0.4. 1.0.4 includes the following: * [MESOS-2537] - AC_ARG_ENABLED checks are broken * [MESOS-6606] - Reject optimized builds

Re: resourceOffer

> Sure, there they are. > > > On Tuesday, March 7, 2017 12:34 PM, Vinod Kone <vinodk...@gmail.com> > wrote: > > > Can you share master log? > > @vinodkone > > On Mar 7, 2017, at 2:54 AM, Oeg Bizz <oegb...@yahoo.com> wrote: > > Hi, >I am new at

Re: [VOTE] Release Apache Mesos 1.1.1 (rc2)

rc2 and back port the perf fix > into 1.1.2. IIUC, time based patch releases should *not be worse*, hence if > the perf issue was already in 1.1.0 it is *fine* to fix it in 1.1.2. I > would like to avoid postponing already belated 1.1.1 for even longer. > > On Wed, Mar 1, 2017 at

Re: [VOTE] Release Apache Mesos 1.2.0 (rc2)

container launch/wait/kill APIs to agent API >> docs. >> >> >> On Wed, Mar 1, 2017 at 11:30 AM, Neil Conway <neil.con...@gmail.com> >> wrote: >> >>> The perf core dump might be addressed if we backport this change: >>> >>> https://r

Re: [VOTE] Release Apache Mesos 1.2.0 (rc2)

Tested on ASF CI. Saw 2 configurations fail. One was the perf core dump issue . Other is a known (since 0..28.0) flaky test with Docker fetcher plugin . Withholding the vote until we know the

Re: [VOTE] Release Apache Mesos 1.1.1 (rc2)

Tested on ASF CI. Saw 2 configurations fail with https://issues.apache.org/jira/browse/MESOS-7160 I think @jpeach and @bbannier were looking into this. Not sure about the severity of the issue, so withholding my vote. *Revision*: b9d8202a7444d0d1e49476bfc9817eb4583beaff -

Re: Question: Modify mesos agent to add custom resources that change dinamically

Don't think that's possible today and I cannot think of easy workarounds for it. On Thu, Feb 9, 2017 at 1:39 AM, Carnero Iglesias, Javier < javier.carn...@atos.net> wrote: > Hi guys, I’ve posted in StackOverflow a *question* >

Re: [VOTE] Release Apache Mesos 1.1.1 (rc1)

+1 (binding) Tested on ASF CI. *Revision*: 5d4c9962930c3f5c08e802caff40b670424cb091 - refs/tags/1.1.1-rc1 Configuration Matrix gcc clang centos:7 --verbose --enable-libevent --enable-ssl autotools [image: Success]

[RESULT][VOTE] Release Apache Mesos 1.0.3 (rc2)

Hi all, The vote for Mesos 1.0.3 (rc2) has passed with the following votes. +1 (Binding) -- Vinod Kone Adam Bordelon Kapil Arya There were no 0 or -1 votes. Please find the release at: https://dist.apache.org/repos/dist/release/mesos/1.0.3

[VOTE] Release Apache Mesos 1.0.3 (rc2)

Hi all, Please vote on releasing the following candidate as Apache Mesos 1.0.3. 1.0.3 includes the following: * [MESOS-6052] - Unable to launch containers on CNI networks on CoreOS * [MESOS-6142] -

Re: Framework stops to receive the heartbeats and events and gets removed from master

No problem. Glad you figured out. @vinodkone > On Jan 23, 2017, at 8:38 AM, Vova Shelgunov wrote: > > Yes, it works. Sorry for troubling, the first time when I looked at the logs > I did not notice that failover_timeout is zero. > > 2017-01-23 19:27 GMT+03:00 Vova

Re: Framework stops to receive the heartbeats and events and gets removed from master

Can you paste the logs or master and framework? @vinodkone > On Jan 23, 2017, at 8:05 AM, Vova Shelgunov wrote: > > Hi, > > I faced a very strange situation with my framework that talks to mesos master > via Scheduler HTTP API: > > Sometimes my framework stops to receive

Welcome Neil Conway as Mesos Committer and PMC member!

Hi folks, Please welcome Neil Conway as the newest committer and PMC member of the Apache Mesos project. Neil has been an active contributor to Mesos for more than a year now. As part of his work, he has contributed some major features (Partition aware frameworks, floating point operations for

Mesos 1.0.3 release

Hi folks, I'm planning to cut 1.0.3 release tomorrow. If you need anything that needs to be backported, please mark the tickets as such. Release dashboard: https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12330112 Thanks, Vinod

Re: Mesos YouTube Channel

Thanks for doing this MPark! On Mon, Jan 9, 2017 at 6:21 PM, Michael Park wrote: > I've created a brand channel for Mesos on YouTube for community activities: > https://www.youtube.com/channel/UC0wxLxgX8ilUn0m31lCpzAw. > > The only community activities currently captured in

Re: Proposal for evaluating Mesos scalability and robustness through stress test.

Great to hear! Haven't looked at the doc yet, but I know some folks from Twitter were also interested this. https://issues.apache.org/jira/browse/MESOS-6768 Probably worth to see if the ideas can be consolidated? On Fri, Jan 6, 2017 at 6:57 PM, Zhitao Li wrote: >

Re: Mesos 1.1.1 release dashboard

Same deal with the next patch release for 1.0.x ;) @vinodkone > On Dec 22, 2016, at 10:15 AM, Alex Rukletsov wrote: > > Folks, > > We are planning to cut the 1.1.1 release early next week. If you have any > patches that need to get into 1.1.1, please make sure that either

Re: Welcome Guangya Liu as Mesos Committer and PMC member!

Congrats Guangya! Welcome to the PMC! On Fri, Dec 16, 2016 at 7:03 PM, Sam wrote: > congratulations Guangya > > Sent from my iPhone > > On 17 Dec 2016, at 3:23 AM, Avinash Sridharan > wrote: > > Congrats Guangya !! > > On Fri, Dec 16, 2016 at 11:20

Welcome Haosdent Huang as Mesos Committer and PMC member!

Hi folks, Please join me in formally welcoming Haosdent Huang as Mesos Committer and PMC member. Haosdent has been an active contributor to the project for more than a year now. He has contributed a number of patches and features to the Mesos code base, most notably the unified cgroups isolator

Re: Quota

"unreserved_resources":{ > "disk":12099.0, > "mem":14863.0, > "gpus":0.0, > "cpus":4.0, > "ports":"[1025-2180, 2182-3887, 3889-5049, > 5052-8

Re: Quota

How many resources does the agent register with the master? How many resources does spark task need? I'm guessing marathon is not registered with "test" role so it is only getting un-reserved resources which are not enough for spark task? On Fri, Dec 9, 2016 at 2:54 PM, Vijay Srinivasaraghavan <

Re: Authentication module

Authentication is enabled for Mesos APIs used by schedulers (to talk to master), operators (to talk to master/agent) and agents (to talk to master). Executor to agent communication is not currently authenticated. This might throw some light:

Re: Force offer from all of the slaves

Once you set GLOG_v, you should be able to see lines like these "Framework filtered agent for <123> seconds" On Sun, Nov 27, 2016 at 8:18 AM, haosdent wrote: > > I choose the right offer and decline the rest. > Hi, @krishnanvr Do you use up all available resources in that

Re: Mesos making offers for no CPU

On Sun, Nov 27, 2016 at 7:53 PM, Christopher Hunt < christopher.h...@lightbend.com> wrote: > My question here though is in the event of receiving a resource offer with > no CPU in it, and then declining it, why shouldn’t my framework receive > offers regarding other nodes with CPU? Surely a

[RESULT][VOTE] Release Apache Mesos 1.0.2 (rc3)

Hi all, The vote for Mesos 1.0.2 (rc3) has passed with the following votes. +1 (Binding) -- Alex Rukletsov Till Toenshoff Yan Xu There were no 0 or -1 votes. Please find the release at: https://dist.apache.org/repos/dist/release/mesos/1.0.2 It is

[VOTE] Release Apache Mesos 1.0.2 (rc3)

Hi all, Please vote on releasing the following candidate as Apache Mesos 1.0.2. This is a bug fix release. The CHANGELOG for the release is available at: https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=1.0.2-rc3

[VOTE] Release Apache Mesos 1.0.2 (rc2)

Hi all, Please vote on releasing the following candidate as Apache Mesos 1.0.2. This is a bug fix release. The CHANGELOG for the release is available at: https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=1.0.2-rc2

Re: outstanding offers

Are you running a custom framework? Can you see in scheduler logs which offers you are receiving? Am I understanding your question correctly that Mesos thinks offers are being sent to your framework but (you think) your framework hasn't received them? Note that you can increase logging on the

Re: On Mesos versioning and deprecation policy

ected by the > breaking API changes. > > On Sat, Oct 15, 2016 at 6:55 AM, Vinod Kone <vinodk...@apache.org> wrote: > > > We will chat about this in the upcoming community sync (thursday 3 PM). > > So, please make sure to attend if you are interested. > > > > On

Re: Does libprocess support multi-port?

No it doesn't. On Wed, Oct 26, 2016 at 1:10 AM, Suteng wrote: > Hi, > > Does libprocess support multi port? Some process bind to a port, and some > other process bind to another port in the same OS process. > > > > Thanks, > > Teng > > > > > > > > > > Su Teng 00241668 > > >

Re: On Mesos versioning and deprecation policy

We will chat about this in the upcoming community sync (thursday 3 PM). So, please make sure to attend if you are interested. On Fri, Oct 14, 2016 at 3:44 PM, Yan Xu wrote: > > On Fri, Oct 14, 2016 at 3:37 PM, Yan Xu wrote: > >> Thanks Alex for starting

Re: 1.1.0 release

I think you need to clean up the JIRA a bit. 1) Make sure unresolved tickets do not have fix version (1.1.0) set. 2) Move "Fix version 1.1.0" to "Target version 1.1.0". 2) might obviate the need for 1). On Fri, Oct 7, 2016 at 7:24 AM, Till Toenshoff wrote: > Hi everyone! >

Re: 1.0.2 release

Release dashboard: https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12329719 I'm waiting for 2 issues to be resolved. Once that's done, I'll start prepping the release. On Wed, Oct 5, 2016 at 4:11 PM, Vinod Kone <vinodk...@apache.org> wrote: > Hi, > > As the

1.0.2 release

Hi, As the Release Manager for 1.0, I'm responsible for all subsequent patch releases. I'm planning to cut the next patch release (1.0.2) within a week. So, if you have any patches that need to get into 1.0.2 make sure that either it is already in the 1.0.x branch or the corresponding ticket has

Re: Target version vs Fixed Version

that check pick this into > 1.0.x. > > On Tue, Oct 4, 2016 at 9:17 AM, Vinod Kone <vinodk...@apache.org> wrote: > >> Hi, >> >> Going forward, if you want an unresolved issue to be targeted for a >> specific version please set the "Target Version". The

Re: Mesos 1.1.0 release date

We are planning to release it in a week or so. Till has agreed to be the release manager for the release and will be supported by AlexR. @Till: Can you create a release dashboard and reply to this thread?

Re: Updating ExecutorInfo after framework failover or best practice

We cannot easily make ExecutorInfo mutable because there might be existing tasks with executors with the old ExecutorInfo. If there are two different ExecutorInfos for the same ExecutorID it gets confusing for Mesos (e.g., SHUTDOWN executor id 'foo' kills which executor?). One possible solution

Re: Threshold-based CPU and Memory Oversubscription

Awesome. Great to see this! Looking forward to the blog post on how this helped utilization in production :P On Wed, Sep 21, 2016 at 10:26 AM, Erb, Stephan wrote: > Hi everyone, > > > > we are happy to announce that we have open sourced two simple > threshold-based

Re: Setting log path for mesos java client library

Looks like Mesos logging flags for these override the corresponding GLOG related flags.

Fwd: REMINDER: MesosCon Asia’s CFP Deadline is September 9! Submit your Proposal Today

Hi folks, Just a friendly reminder that the CFP for MesosCon Asia is fast approaching! If you were planning to submit a talk please do so ASAP. If you weren't, please do :) Thanks, Vinod -- Forwarded message -- From: Linux Foundation Events Date:

Re: mesos libraries

If you are writing a new scheduler, I would highly recommend using the new HTTP API instead of the Java bindings. This would eliminate the dep on the native library. If you still want to use the old bindings, the easiest way might be to install mesos deb package in your docker image. On Tue, Aug

Re: Mesos logging

Did you figure this out? AFAICT, the LOG(INFO) line should be printed in agent logs. What agent flags are you using? On Tue, Aug 9, 2016 at 8:19 AM, Hendrik Haddorp wrote: > I saw a few "Running ..." log entries from the docker support code but > they seem to be all

[VOTE] Release Apache Mesos 1.0.1 (rc1)

Hi all, Please vote on releasing the following candidate as Apache Mesos 1.0.1. The CHANGELOG for the release is available at: https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=1.0.1-rc1

Re: Support for tasks groups aka pods in Mesos

Sorry, sent the wrong link earlier for design doc. Design doc: https://issues.apache.org/jira/browse/MESOS-6009 > Direct link: https://docs.google.com/document/d/1FtcyQkDfGp-bPHTW4pUoqQCgVlPde936bo-IIENO_ho/edit#heading=h.ip4t59nlogfz

Support for tasks groups aka pods in Mesos

Hi folks, One of the most requested features in Mesos has been first class support for managing pod like containers. We finally have some time to focus and shepherd this work. The epic tracking this work is : https://issues.apache.org/jira/browse/MESOS-2449 Design doc:

1.0.1 release

Hi, As discussed on the 1.0 voting thread, we plan to cut a 1.0.1 as early as this week. So if you have anything that needs to absolutely go into the patch release, please work with your shepherd and get it landed on trunk and backported to the 1.0.x branch. Thanks,

Re: Enabling basic access authentication

We separated out the default authentication mode for read only (default: no authn) and read-write (default: authn) endpoints. Since the webui only depends on the read-only endpoints you need to explicitly enable authn for read-only endpoints if you need authn. See

Re: [RESULT][VOTE] Release Apache Mesos 1.0.0 (rc4)

The 1.0 blog post is up: http://mesos.apache.org/blog/mesos-1-0-0-released/ Thank you all for making this possible! @vinodkone > On Jul 27, 2016, at 7:39 AM, Vinod Kone <vinodk...@apache.org> wrote: > > Hi all, > > The vote for Mesos 1.0.0 (rc4) has passed wit

[RESULT][VOTE] Release Apache Mesos 1.0.0 (rc4)

os-1.0.0.jar has been released to: https://repository.apache.org The website (http://mesos.apache.org) will be updated shortly to reflect this release. Thanks, On Fri, Jul 22, 2016 at 10:40 PM, Vinod Kone <vinodk...@apache.org> wrote: > Hi all, > > > Please vote on rel

Re: [VOTE] Release Apache Mesos 1.0.0 (rc4)

in CentOS 7.2 > * make check in Ubuntu 14.04 > * test upgrade from 0.28.2 to 1.0.0-rc4 > > > On Tue, Jul 26, 2016 at 8:33 AM, Kapil Arya <ka...@mesosphere.io> > > wrote: > > > One can find the deb/rpm packages here: > > http://open.mesosphere.com/downloads/me

[VOTE] Release Apache Mesos 1.0.0 (rc4)

Hi all, Please vote on releasing the following candidate as Apache Mesos 1.0.0. *The vote is open until Tue Jul 25 11:00:00 PDT 2016 and passes if a majority of at least 3 +1 PMC votes are cast.* 1.0.0 includes the following:

Re: [VOTE] Release Apache Mesos 1.0.0 (rc3)

Looks like we missed a cherry pick. I'm cancelling this vote and spinning up rc4. On Fri, Jul 22, 2016 at 2:24 PM, Vinod Kone <vinodk...@apache.org> wrote: > Hi all, > > > Please vote on releasing the following candidate as Apache Mesos 1.0.0. > > *The vote is open until

[VOTE] Release Apache Mesos 1.0.0 (rc3)

Hi all, Please vote on releasing the following candidate as Apache Mesos 1.0.0. *The vote is open until Tue Jul 25 11:00:00 PDT 2016 and passes if a majority of at least 3 +1 PMC votes are cast.* 1.0.0 includes the following:

Re: Possible authentication bug

On Thu, Jul 21, 2016 at 4:49 PM, Douglas Nelson wrote: > Just out of curiosity, is there a rough ETA for the stable release of > 1.0.0? Or is anyone currently using rc2 in production? > I'm hoping to cut RC3 later today or tomorrow and barring any -ve votes do the official

Re: Possible authentication bug

Might be related to MESOS-2043 ? Can you paste master and agent logs? On Mon, Jul 18, 2016 at 3:13 PM, Douglas Nelson wrote: > I have SSL enabled for mesos and for the most part everything seems to be > working fine. But

Re: mesos agent not recovering after ZK init failure

On Fri, Jul 15, 2016 at 11:31 AM, Sharma Podila wrote: > We had this issue happen again and were able to debug further. The cause > for agent not being able to restart is that one of the resources (disk) > changed its total size since the last restart. However, this error

Re: test

Don't sweat about the test email. Not a big deal. Welcome to the community! On Wed, Jul 13, 2016 at 1:51 PM, Rahul Palamuttam wrote: > I'm truly sorry. > Just kept getting several message denied errors, until I realized I needed > to send a reply to user-subscribe. > I

Re: How to send a task to a running framework?

Are you asking how users can submit their tasks to your custom framework? Your framework should probably expose an API for that. On Fri, Jul 8, 2016 at 4:30 AM, Bryan Fok wrote: > Hi all > > After I have my custom framework running in , for instance, a python > process

[VOTE] Release Apache Mesos 1.0.0 (rc2)

Hi all, Please vote on releasing the following candidate as Apache Mesos 1.0.0. 1.0.0 includes the following: * Scheduler and Executor v1 HTTP APIs are now considered stable. * [MESOS-4791] -

Re: 1.0.0 RC2

=12328715 On Tue, Jun 21, 2016 at 11:48 AM, Vinod Kone <vinodk...@apache.org> wrote: > There are still 8 outstanding issues, including 1 blocker. We are waiting > for these to land for RC2. > > > On Fri, Jun 17, 2016 at 5:11 PM, Vinod Kone <vinodk...@apache.org> wrote: &

<    1   2   3   4   5   6   >