Re: Help us review #MesosCon 2015 proposals

+1 It does not allow me to continue to see the second page if I don't make choices on the first one. - Jie On Fri, Feb 20, 2015 at 4:54 PM, Benjamin Mahler wrote: > Great to see so many proposals! > > Is it intentional that we have to review them in small subsets? It's hard > to tell what to c

Re: SharedFilesystem and rolling restarts

Hi, in Mesos 0.23.0 (the next release), you'll be able to use the persistence primitives provided by Mesos. https://issues.apache.org/jira/browse/MESOS-1554 Basically, your framework can create a persistent volume (has a unique handle) while launching a task and re-use that handle when re-launchin

Re: [DISCUSS] Renaming Mesos Slave

Adam, If a vote is called out, how do we decide if it passes or not. Will that be the same of voting for a release (i.e., PMC member can veto it)? I would imagine that some PMC members might want to express some negative feedbacks on this, but certainly do not want to veto it. How do we deal with

Re: [DISCUSS] Renaming Mesos Slave

consideration the overhead any change > may have on any adopter/organization and discuss those risks and > problems openly, but ideally this decision would be made based upon > consensus within the community. If consensus cannot be reached, a vote > among committers may be necessary. >

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

Jeff, Can you use --verbose during testing and paste the log? - Jie On Thu, Jul 9, 2015 at 11:02 AM, Jeff Schroeder wrote: > Does anyone else see this python failure, or am I just testing something > incorrectly? > > On Wed, Jul 8, 2015 at 7:33 PM, Jeff Schroeder > wrote: > >> -1 (non-binding

Re: Reusing Task IDs

Re-using Task IDs is definitely not encouraged. As far as I know, many of the Mesos code assume Task ID is unique. So I probably won't risk that. On Fri, Jul 10, 2015 at 10:06 AM, Sargun Dhillon wrote: > Is reusing Task IDs good behaviour? Let's say that I have some > singleton task - I'll call

Re: Disk Capacity Detection

Chris, Mesos currently only supports a single disk. In other words, if you have multiple disks, Mesos can only manage one of them. You can choose which disk to use by setting --work_dir to the appropriate directory under the given disk. On Thu, Jul 23, 2015 at 2:28 PM, Christopher Ketchum wrote:

SharedFilesystemIsolator (filesystem/shared)

Hi Mesos users, I am wondering if anyone is using this isolator (i.e., --isolation=filesystem/shared)? If not, we plan to remove it from the source code in favor of using the upcoming more general linux filesystem isolator (https://reviews.apache.org/r/36429/). - Jie

Re: Improvements to container support with custom executor

Kevin, Thanks for bringing this up! This question is related to the work we are currently doing for Filesystem Isolation (MESOS-2386 ) and Unified Container ( MESOS-2840 ). In fact, if you think ab

Re: Improvements to container support with custom executor

one of the least reliable > components of the ecosystem (the Docker daemon) while preserving the > illusion of Docker to our end users. > > On Aug 14, 2015, at 12:17 PM, Jie Yu wrote: > > > Kevin, > > > > Thanks for bringing this up! This question is related to

Re: MesosCon Seattle attendee introduction thread

Hey there! I'm Jie Yu (@jie_yu), a Software Engineer at Twitter and a Mesos committer. I'll be giving two talks at the conference. If you're interested in the persistence primitives recently introduced (link <http://sched.co/35Cq>), or the built-in production quality netw

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

Niklas, This is the known problem reported by Marco. I am OK with both because the linux filesystem isolator cannot be used in 0.24.0. If you guys prefer to cut another RC, here is the patch that needs to be cherry picked: commit 3ecd54320397c3a813d555f291b51778372e273b Author: Greg Mann Date:

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

ncountered with RC1? > > > > > > > > On Thu, Aug 27, 2015 at 3:45 PM, Niklas Nielsen > > wrote: > > > >> If it is that easy to fix, why not get it in? > >> > >> How about https://issues.apache.org/jira/browse/MESOS-3053 (which > &g

Removing external containerizer from code base

Hey guys, Per discussion in MESOS-3370 , I'll start removing the external containerizer and cleaning up the relevant code. Please let me know if you have any concern. Thanks! - Jie

Re: Removing external containerizer from code base

tion to use ECP seemed attractive. > Can you, please, elaborate on the implications of having our own > containerizer without ECP? I assume we would have to implement it in cpp, > it might require recompiling (parts of) Mesos, some other things? > > Thanks, > Alex > > > &g

Re: Apache Mesos Community Sync

Adam, since most of the Twitter folks are OOO this week. I chatted with Artem/Vinod. we think it makes sense to host the sync at Mesosphere tomorrow. - Jie On Wed, Nov 4, 2015 at 4:22 PM, Adam Bordelon wrote: > It's been a while since our last community sync, and tomorrow, Thursday > Nov 5th sh

Re: Welcome Kapil as Mesos committer and PMC member!

Congrats Kapil! On Thu, Nov 5, 2015 at 2:02 AM, Till Toenshoff wrote: > I'm happy to announce that Kapil Arya has been voted a Mesos committer and > PMC member! > > Welcome Kapil, and thanks for all of your great contributions to the > project so far! > > Looking forward to lots more of your con

Re: Fate of slave node after timeout

> > Can that slave never again be added into the cluster, i.e., what happens > if it comes up 1 second after exceeding the timeout product? It'll not be added to the cluster. The master will send a Shutdown message to the slave if it comes up after the timeout. - Jie On Fri, Nov 13, 2015 at 1:4

Re: Fate of slave node after timeout

7;s odd behavior, no? That would seem to mean that the slave can never > again join the cluster, at least not from it's original IP@. > > What if the master bounces? Will it then tolerate the slave? > > -Paul > > On Nov 13, 2015, at 4:46 PM, Jie Yu wrote: > > Can t

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

Niklas, I think Joris is still working on the user doc for multi-disk support in Mesos. - Jie On Thu, Feb 4, 2016 at 1:22 AM, Niklas Nielsen wrote: > Awesome guys! > > Kapil, we usually linked to the user documentation in the blog to the new > features. Do you have a link to the docs on multip

Re: Question regarding docker containerizer

You can take a look at the TaskInfo. If the TaskInfo does not have ExecutorInfo set, then it's a task. Otherwise, Mesos will launch the executor and send the task to the executor. - Jie On Thu, Feb 25, 2016 at 2:50 PM, Pradeep Chhetri < pradeep.chhetr...@gmail.com> wrote: > Hello, > > From docke

Re: Question regarding docker containerizer

er ? Can i see the TaskInfo > details in the mesos master UI for a task? > > On Thu, Feb 25, 2016 at 10:52 PM, Jie Yu wrote: > >> You can take a look at the TaskInfo. If the TaskInfo does not have >> ExecutorInfo set, then it's a task. Otherwise, Mesos will launch th

Re: Question regarding docker containerizer

;: 31050,"container_port": 5601,"protocol": " > tcp"}],"privileged": false,"parameters": [{"key": "publish-all","value": " > true"}],"force_pull_image": true}}}, > > > > On Thu, F

Making 'curl' a prerequisite for installing Mesos

Hi, I am proposing making 'curl' a prerequisite when installing Mesos. Currently, we require 'libcurl' being present when installing Mesos ( http://mesos.apache.org/gettingstarted/). However, we found that it does not compose well with our asynchronous runtime environment (i.e., it'll block the cu

Re: Making 'curl' a prerequisite for installing Mesos

xxx() APIs explored? > > Neil > > On Thu, Mar 3, 2016 at 9:10 AM, Jie Yu wrote: > > Hi, > > > > I am proposing making 'curl' a prerequisite when installing Mesos. > > Currently, we require 'libcurl' being present when installing Mesos > &

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

I am writing that as you speaking On Fri, Mar 4, 2016 at 10:34 AM, Vinod Kone wrote: > I think this was supposed to refer to > https://github.com/apache/mesos/blob/master/docs/mesos-containerizer.md > > @Jie ^^ ? > > On Fri, Mar 4, 2016 at 10:29 AM, Steven Schlansker < > sschlans...@opentable.co

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

I will rename mesos-provisioner.md -> container-image.md, and do some re-writing. - Jie On Fri, Mar 4, 2016 at 10:35 AM, Jie Yu wrote: > I am writing that as you speaking > > On Fri, Mar 4, 2016 at 10:34 AM, Vinod Kone wrote: > >> I think this was supposed to refer to

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

Steven, sorry about the delay. I'll finish the doc today. On Fri, Mar 4, 2016 at 10:29 AM, Steven Schlansker < sschlans...@opentable.com> wrote: > > > On Mar 3, 2016, at 5:43 PM, Vinod Kone wrote: > > > > Hi all, > > Please vote on releasing the following candidate as Apache Mesos 0.28.0. > > 0.

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

I'd like to fix https://issues.apache.org/jira/browse/MESOS-4888 as well if you guys plan to cut another RC On Mon, Mar 7, 2016 at 10:16 AM, Daniel Osborne < daniel.osbo...@metaswitch.com> wrote: > -1 > > If it doesn’t cause too much pain, I'm hoping we can squeeze a relatively > small patch whic

Re: Executors no longer inherit environment variables from the agent

Alex, See my response inlined: First, does this change include the executor library? We currently use > environment variables to propagate various config values from an agent to > executors. If it does, what is the alternative? Any environment variables generated by Mesos (i.e., MESOS_, LIBPROC

Re: Executors no longer inherit environment variables from the agent

Rodrick, This is unfortunate we are using environment variables that get passed into > the executors context such as > CHRONOS_RESOURCE_MEM > MARATHON_APP_RESOURCE_MEM > What will be the workaround? Those env vars are set when launching the agent? Can you use --executor_environment_variables to

0.28.1

Hi, We recently noticed two bugs in 0.28.0 related to the unified containerizer: Because of that, I propose we cut a point release (0.28.1) once these tw

Re: Unstability on Mesos 0.27

Thanks for reporting! Can you be more specific about which component crashes a lot? Is it the framework, the master, the agent, or the executor. As Artem and Vinod mentioned, it'll be really helpful if you can provide the relevant log (master/agent/executor's log) so that we can pinpoint the issue.

[VOTE] Release Apache Mesos 0.17.0 (rc2)

Hi all, Please vote on releasing the following candidate as Apache Mesos 0.17.0. 0.17.0 includes the following: The primary feature of this release is to add recovery support for replicated log to make it more resil

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

Hi all, The vote for Mesos 0.17.0 (rc2) has passed with the following votes. +1 (Binding) -- Benjamin Mahler Niklas Nielsen Vinod Kone There were no 0 or -1 votes. Please find the release at: https://dist.apache.org/repos/dist/release/mesos/0.17.0 It is recommended

Re: http://mesos.apache.org/downloads/ is saying the latest release is 0.16.0

Chengwei, Thank you for letting us know! We are currently working on the blog post for the 0.17.0 release. We'll update the homepage once the blog post is done (in 1 week). - Jie On Thu, Mar 6, 2014 at 12:19 PM, Benjamin Mahler wrote: > +jie who has been doing the 0.17.0 release > > > On Wed,

Re: [VOTE] Release Apache Mesos 0.18.0 (rc6)

+1 make check on OSX and CentOS 5 - Jie On Tue, Apr 8, 2014 at 3:55 PM, Brenden Matthews < brenden.matth...@airbedandbreakfast.com> wrote: > +1! > > > On Thu, Apr 3, 2014 at 9:00 AM, Tim St Clair wrote: > > > make check passes, and setup mini cluster so, +1 > > > > ---

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

+1 make check passed on centos 6 with gcc44 mac os x 10.8 with gcc48 - Jie On Wed, May 14, 2014 at 12:06 PM, Niklas Nielsen wrote: > Hi all, > > Please vote on releasing the following candidate as Apache Mesos 0.18.2. > > > 0.18.2 includes the following: > > -

Re: Dealing with "run away" task processes after executor terminates

milar clean up behavior? > > > On Tue, Jun 3, 2014 at 5:44 PM, Vinod Kone wrote: > >> +Jie,Ian >> >> Not sure if you've talked to Ian Downes and/or Jie Yu regarding this but >> they were discussing the same issue (offline) today. >> >> Just to be s

Re: n00b isolation docs?

Hi Dick, > what croup isolation provides over stock posix / process isolation Currently, mesos provides cpu and memory isolation through cgroups on Linux boxes '--isolation=cgroups/cpu,cgroups/mem' the configuration required to setup cgroups If no other service on the host uses cgroup (no cg

Re: Apache Mesos 0.19.0 Released

gt; >> > >> Thanks to the Registrar, reconciliation primitives can now be provided > to > >> ensure that the state of tasks between Mesos and frameworks is kept > >> consistent. This will remove the need for frameworks to implement > >> out-of-band task reco

Re: Apache Mesos 0.19.0 Released

one from wiring up the existing >> ZooKeeper storage implementation in Mesos and providing it as an >> alternative to the replicated log. As soon as we provide two we should have >> tooling to allow people to move between them. >> >> I hope this clarifies things! >>

Re: Quorum in mesos 19

Hi Diptanu, If you choose to use the replicated log as the backend for registrar , you're gonna tell each master how many masters are there in the cluster. Each registr

Re: number of masters and quorum

Dick, you are right. - Jie On Tue, Jul 1, 2014 at 3:20 PM, Dick Davies wrote: > I might be wrong but doesn't the new quorum setting mean > it only makes sense to run an odd number of masters > (a la zookeepers)? > > i.e. 4 masters is no more resilient than 3 (in fact less so, since > you incre

Re: Does Mesos support Hadoop MR V2

I am interested in investigating the idea of YARN on top of Mesos. One of the benefits I can think of is that we can get rid of the static resource allocation between YARN and Mesos clusters. In that way, Mesos can allocate those resources that are not used by YARN to other Mesos frameworks like Au

Re: Python bindings are changing!

Thomas, Thank you for the heads-up. One question: what if mesos and python binding have different versions? For example, is it ok to use a 0.19.0 python binding and having a 0.20.0 mesos? Same question for the reverse. - Jie On Fri, Aug 1, 2014 at 9:37 AM, Thomas Rampelberg wrote: > - What pr

0.20.0

Hi all, In the coming weeks, we would like to cut 0.20.0 on the master branch. I would like to volunteer to be the release manager. I've created a ticket to help track any dependencies: https://issues.apache.org/jira/browse/MESOS-1645 There are a few features will go out in this release: Docker

Re: Python bindings are changing!

functionality is coming from libmesos itself. It might work to use >> 0.19 with a 0.20 mesos (or visa versa), but there be dragons =) >> >> >> On Fri, Aug 1, 2014 at 1:30 PM, Jie Yu wrote: >> > Thomas, >> > >> > Thank you for the heads-up.

[VOTE] Release Apache Mesos 0.20.0 (rc1)

Hi all, Please vote on releasing the following candidate as Apache Mesos 0.20.0. 0.20.0 includes the following: This release includes a lot of new cool features. The major new features are listed below: * Docker su

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

acosx-10.9-x86_64.egg-tmp/mesos/native/_mesos.so > > Expected in: flat namespace > > in > /Users/vinod/.python-eggs/mesos.native-0.20.0-py2.7-macosx-10.9-x86_64.egg-tmp/mesos/native/_mesos.so > > tests/script.cpp:83: Failure > > Failed > > python_framework_test.sh ex

[VOTE] Release Apache Mesos 0.20.0 (rc2)

Hi all, Please vote on releasing the following candidate as Apache Mesos 0.20.0. NOTE: 0.20.0-rc1 has a bug on Mac (MESOS-1713) which is fixed in 0.20.0-rc2. 0.20.0 includes the following: This release includes a l

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

4/egg/mesos/native/_mesos.py", line 7, in > > File "build/bdist.linux-x86_64/egg/mesos/native/_mesos.py", line 6, in > __bootstrap__ > ImportError: > /home/tstclair/.python-eggs/mesos.native-0.20.0-py2.7-linux-x86_64.egg-tmp/mesos/native/_mesos.so: > undefined symbol: _ZN6g

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

Synced with Tim. We both think this shouldn't be a blocker for the release. - Jie On Tue, Aug 19, 2014 at 7:21 PM, Jie Yu wrote: > Tim, I demangled the symbol: > > google::FlagRegisterer::FlagRegisterer(char const*, char const*, char > const*, char const*, void*, void*) >

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

Qian, can you fire a bug report with logs (also, please turn on verbose logging during testing). - Jie On Thu, Aug 21, 2014 at 7:05 PM, Qian Zhang wrote: > Thanks Tim. > > However I am not sure if they are the same issue. What I reported is when > I run "make check" on RHEL 7, it failed at DRF

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

Hi all, The vote for Mesos 0.20.0 (rc2) has passed with the following votes. +1 (Binding) -- Vinod Kone Ian Downes Niklas Nielsen Tim St Clair +1 (Non-binding) -- Timothy Chen There were no 0 or -1 votes. Please find the release at: https

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

ote: >> > I seem to be missing the 0.20-rc2 and 0.20 release tags in git. >> > >> > -h >> > >> > >> > >> > On Thu, Aug 21, 2014 at 11:59 PM, Jie Yu wrote: >> >> Hi all, >> >> >> >> The vote for Mesos 0

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

fast.com> wrote: > Hey Jie, > > I'm not seeing the jar in the maven repo: > > > http://search.maven.org/#search%7Cgav%7C1%7Cg%3A%22org.apache.mesos%22%20AND%20a%3A%22mesos%22 > > Did something go awry when publishing the jar? > > > On Sun, Aug 24, 2014 at 4:41 PM,

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

meantime, I've manually added > the repo to my pom. > > > On Mon, Aug 25, 2014 at 5:33 PM, Jie Yu wrote: > >> Brenden, >> >> The jar has definitely been submitted: >> https://repository.apache.org/index.html#nexus-search;quick~mesos >> >>

Re: Mesos-slave 0.20.0 fails to register in mesos-master if containerizers=docker,mesos, works with containerizers=mesos

I0827 22:58:18.789118 3383 docker.cpp:649] Recovering Docker containers Seems that the slave stuck at recovering docker containers. - Jie On Wed, Aug 27, 2014 at 2:00 PM, Javier Ruiz Jiménez wrote: > Hi all, > > My first post in the user list. Writing from Spain. > > I am setting up a Mesos

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

+1 (binding) Make check on centos5 and centos6 (gcc48) On Thu, Sep 18, 2014 at 4:05 PM, Adam Bordelon wrote: > Hi all, > > Please vote on releasing the following candidate as Apache Mesos 0.20.1. > > > 0.20.1 includes the following: > > --

Re: Mesos Compilation error

I think this is a bug. We forgot to include that header file in libmesos_no_3rdparty_la_SOURCES. Could you please open a ticket? To workaround, you can checkout the source from git using tag 0.20.1. - Jie On Wed, Oct 1, 2014 at 12:46 PM, Diptanu Choudhury wrote: > Hi Guys, > > We are trying to

Re: Mesos Compilation error

Just committed a fix to the master. On Wed, Oct 1, 2014 at 12:50 PM, Jie Yu wrote: > I think this is a bug. We forgot to include that header file in > libmesos_no_3rdparty_la_SOURCES. Could you please open a ticket? > > To workaround, you can checkout the source from git usin

Re: Mesos Compilation error

a/browse/MESOS-1855 >>> >>> On Wed, Oct 1, 2014 at 1:20 PM, Diptanu Choudhury >>> wrote: >>> >>>> Thanks, opening a ticket now. So I am trying to compile from - >>>> https://github.com/apache/mesos/archive/0.20.1.tar.gz >>&

Re: Mesos Compilation error

> ubuntu trusty package repo didn't have the libnl3 3.2.25, but had some > older version. > > > Any idea how I could fix it? > > On Wed, Oct 1, 2014 at 2:44 PM, Jie Yu wrote: > >> Yeah, the header is from libnl3. >> >> Can you post the location where your l

Re: Mesos Compilation error

configure.ac: LIBNL_CFLAGS=-I/usr/include/libnl3 Is it possible to install your libnl3 to --prefix=/usr ? On Wed, Oct 1, 2014 at 3:06 PM, Jie Yu wrote: > Hum, we expect libnl3 headers to be installed under /usr/include/libnl3: > > > On Wed, Oct 1, 2014 at 2:51 PM, Diptanu Choudh

Re: Mesos Compilation error

I'll create a ticket for supporting customized libnl3 install location. On Wed, Oct 1, 2014 at 3:07 PM, Jie Yu wrote: > configure.ac: > LIBNL_CFLAGS=-I/usr/include/libnl3 > > Is it possible to install your libnl3 to --prefix=/usr ? > > On Wed, Oct 1, 2014 at 3:06 PM, Jie

Re: Rocket

Sounds great Tim! Do you know if they have published an API for the rocket toolset? Are we gonna rely on the command line interface? - Jie On Mon, Dec 1, 2014 at 11:10 AM, Tim Chen wrote: > Hi all, > > Per the announcement from CoreOS about Rocket ( > https://coreos.com/blog/rocket/) , it seem

Re: Resize Mesos master quorum

+ BenM Ben, I remembered that you planed to add it some time before? - Jie On Thu, Dec 18, 2014 at 11:42 AM, Steven Schlansker < sschlans...@opentable.com> wrote: > > I'm looking to be able to increase (3 -> 5) and decrease (5 -> 3) the > number of Mesos masters I run. > There doesn't seem to be

Re: Does mesos support running two slaves on a single host?

The caveat here is that some launcher/isolators assume one slave per host. For instance, you cannot use Linux launcher and cgroups isolators if you want to launch multiple slaves per host. So in general, we don't recommend users to do that. - Jie On Tue, Mar 22, 2016 at 9:35 AM, Dan Leary wrot

Re: 0.28.1

other patches for 0.28.1, please contact me asap. Thanks! - Jie On Wed, Mar 23, 2016 at 8:35 PM, Benjamin Mahler wrote: > Thanks Jie, I've added a fix version of 0.28.1 to: > https://issues.apache.org/jira/browse/MESOS-5021 > > On Fri, Mar 18, 2016 at 5:52 PM, Jie Yu wrote: >

[VOTE] Release Apache Mesos 0.28.1 (rc1)

Hi all, Please vote on releasing the following candidate as Apache Mesos 0.28.1. 0.28.1 includes the following: *Announce major features here* *Announce major bug fixes here* The CHANGELOG for the r

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

oops. I forgot to include the change log in the release. Please ignore this email. I'll cut rc2 :( - Jie On Tue, Apr 5, 2016 at 6:15 PM, Jie Yu wrote: > Hi all, > > Please vote on releasing the following candidate as Apache Mesos 0.28.1. > > > 0.28.1

[VOTE] Release Apache Mesos 0.28.1 (rc2)

Hi all, Please vote on releasing the following candidate as Apache Mesos 0.28.1. 0.28.1 includes the following bug fixes: [MESOS-4662] - PortMapping network isolator should not assume BIND_MOUNT_ROOT is a realpath.

Re: SharedFilesystemIsolator (filesystem/shared)

"RW"}, > {"host_path": "system/vartmp", "container_path": > "/var/tmp","mode": "RW"} > ] > } > > ​ > > We are running on linux, so I guess the new one will work for

Re: SharedFilesystemIsolator (filesystem/shared)

ailable in > this ticket: https://issues.apache.org/jira/browse/MESOS-5187​ > > > Best Regards, > Stephan > ---------- > *From:* Jie Yu > *Sent:* Monday, April 11, 2016 17:37 > > *To:* user@mesos.apache.org > *Subject:* Re: SharedFilesystemIsolator

Re: [Proposal] Remove the default value for agent work_dir

+1 On Tue, Apr 12, 2016 at 9:29 PM, James Peach wrote: > > > On Apr 12, 2016, at 3:58 PM, Greg Mann wrote: > > > > Hey folks! > > A number of situations have arisen in which the default value of the > Mesos agent `--work_dir` flag (/tmp/mesos) has caused problems on systems > in which the autom

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

Hi all, The vote for Mesos 0.28.1 (rc2) has passed with the following votes. +1 (Binding) -- Michael Park Vinod Kone Kapil Arya +1 (Non-binding) -- Greg Mann There were no 0 or -1 votes. Please find the release at: https://dist.apache.org

Re: Mesos on RHEL 5.X

I know someone is still using Mesos in production on RHEL 5.4. You need devtoolset-2 to build Mesos. On Tue, Apr 19, 2016 at 10:50 AM, Jeff Schroeder wrote: > The RHEL5 kernel will not support the necessary bits for mesos. RHEL6 also > lacks the overwhelming majority of support for namespaces an

0.28.2

Hi folks, According to our release schedule, we should be cutting point release for 0.28.x. I volunteer to be the release manager. Vinod and Ben already started a branch (0.28.x) in the repo, so it's just a matter of cutting it. If you have any patch that you want to backport into 0.28.2, please l

Re: 1.0 Release Candidate

Jeff, Yes, deprecating the docker containerizer will be post-1.0. The plan has not changed. In fact, we are making very good progress on the unified containerizer side (see this doc ). We'll continue to support Docker containeri

Re: 0.28.2

or this particular fix to land: > https://issues.apache.org/jira/browse/MESOS-4705. > > Thanks! > > -- Roger > > On Tue, May 24, 2016 at 9:04 AM, Jie Yu wrote: > >> Hi folks, >> >> According to our release schedule, we should be cutting point release for

Re: 0.28.2

OK, looks like no one volunteer for 0.27.3 and 0.26.2. Therefore, I'll be the release manager for these two release as well. Will try to cut right after MesosCon. - Jie On Fri, May 27, 2016 at 9:38 AM, Jie Yu wrote: > Any other committers have cycles for point release 0.27.3 and 0.

Re: 0.28.2

; June Taylor > System Administrator, Minnesota Population Center > University of Minnesota > > On Tue, May 24, 2016 at 11:04 AM, Jie Yu wrote: > >> Hi folks, >> >> According to our release schedule, we should be cutting point release for >> 0.28.x. I volunteer

[VOTE] Release Apache Mesos 0.28.2 (rc1)

Hi all, Please vote on releasing the following candidate as Apache Mesos 0.28.2. 0.28.2 is a bug fix release. It includes the following: ** Bug * [MESOS-4705] - Linux 'perf' parsing logic may fail when OS distribu

[RESULT][VOTE] Release Apache Mesos 0.28.2 (rc1)

Hi all, The vote for Mesos 0.28.2 (rc1) has passed with the following votes. +1 (Binding) -- Vinod Kone Till Toenshoff Kapil Arya +1 (Non-binding) -- Guangya Liu haosdent There were no 0 or -1 votes. Please find the release at: https://di

Re: Mesos HA does not work (Failed to recover registrar)

Which version are you using? - Jie On Sat, Jun 4, 2016 at 4:34 PM, Qian Zhang wrote: > Thanks Vinod and Dick. > > I think my 3 ZK servers have formed a quorum, each of them has the > following config: > $ cat conf/zoo.cfg > server.1=192.168.122.132:2888:3888 > server.2=192.168.122.2

0.28.2 has been released

Hi folks, I just released Mesos 0.28.2 and updated the website. It includes some important bug fixes. The change log can be found here: https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_plain;f=CHANGELOG;hb=0.28.2 If you are considering using 0.28, please use 0.28.2! Thanks! - Jie

Proposal: move content in Wiki to docs in code repo

Hi folks, I am proposing moving our content in Wiki (e.g., working groups, release tracking, etc.) to our docs in the code repo. I personally found that wiki is hard to use and there's no reviewing process for changes in the Wiki. The content in Wiki historically received less attention than that

[VOTE] Release Apache Mesos 0.27.3 (rc1)

Hi all, Please vote on releasing the following candidate as Apache Mesos 0.27.3. NOTE: I fat fingered and accidentally released the 0.27.3 jar to maven repo and I have no permission to remove it (apologies!). If this vote passes, nothing needs to be done. If not, I'll see how I can update it. Sor

Re: Proposal: move content in Wiki to docs in code repo

>>>> IBM China Software Development Laboratory (CSDL) >>>> Notes ID:Zhou Z Xing/China/IBM >>>> Phone :86-10-82450442 >>>> e-Mail :xingz...@cn.ibm.com >>>> Address :Building No.28, ZhongGuanCun Software Park, No.8 Dong Bei Wang &g

Re: Mesos 0.28.2 does not start

Can u create a jira ticket and paste the master log? Thanks for reporting! Sent from my iPhone > On Jun 10, 2016, at 8:44 AM, Stefano Bianchi wrote: > > Hi all > i'm re installing my platform on another openstack tenant. > I downloaded all the needed softwares, zookeeper-server, mesos 0.28.2 >

[RESULT][VOTE] Release Apache Mesos 0.27.3 (rc1)

Hi all, The vote for Mesos 0.27.3 (rc1) has passed with thefollowing votes. +1 (Binding)--Kapil Arya Vinod Kone Benjamin Mahler +1 (Non-binding)--Jörg Schad There were no 0 or -1 votes. Please find the release at: https://dist.apache.org/rep

Mesos working groups

Hi, I am in the process of formalizing our working groups. We recently moved our working groups wiki to documentation in the repo (Thanks Tomasz!). That'll give us more visibility hopefully. https://github.com/apache/mesos/blob/master/docs/working-groups.md However, I realized that a lot of the w

Re: Mesos working groups

uted file systems supported or > to be supported? HDFS, S3, OrangeFS etc? > > Maybe some descriptors on each working-group as to clarify the > area(s) covered by the working group, or that info is already in the wiki? > > > > James > > > > > > On 06/16/2016 12:

Re: Shell Environment Variables

Hansel, I think it was definitely not intentional. I am wondering what happens if the user does not have a home directory, what should $HOME be? - Jie On Fri, Jun 17, 2016 at 9:08 AM, wrote: > Hi Haosdent, > > Yes, I had confirmed that setuid does get called correctly, and the shell > environme

Re: Shell Environment Variables

Another note is that Mesos task should only write to its sandbox ($MESOS_SANDBOX). Not sure what's the use case for getting $HOME. On Fri, Jun 17, 2016 at 10:10 AM, Jie Yu wrote: > Hansel, I think it was definitely not intentional. I am wondering what > happens if the user does not

Re: Order of URIs in CommandInfo protobuf

There is no ordering assumption in the API. - Jie On Fri, Jun 17, 2016 at 10:33 AM, Wil Yegelwel wrote: > I'm curious whether there is an ordering assumption on the CommandInfo > protobuf or if the order does not matter. The comment in mesos.proto, "Any > URIs specified are fetched before execu

Re: Mesos CLI

Haris, i think you meant to make a backward incompatible change to the existing commands, not removing them, right? For instance: mesos ps -> mesos cluster ps mesos cat -> mesos cluster cat I guess the question is: is there anyone use those tools in production and their tooling depends on those c

[VOTE] Release Apache Mesos 0.26.2 (rc1)

Hi all, Please vote on releasing the following candidate as Apache Mesos 0.26.2. 0.26.2 is a bug fix release. It includes the following: [MESOS-4705] - Linux 'perf' parsing logic may fail when OS distribution has pe

Re: Executors no longer inherit environment variables from the agent

FYI, from Mesos 1.0, the executors will no longer inherit environment variables from the agent by default. If you have environment environment variables that you want to pass in to executors, please use `-- executor_environment_variables` flag on the agent. commit ce4b3056164a804bea52810173dbd7a41

  1   2   3   >