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

+1 (non binding) Debian 8 (jessie) plain non root OK. Mac OS X plain non root OK. Ubuntu 14.04 plain/SSL with root and docker-engine 1.10: Only flaky test I observed on Ubuntu 14.04 is HealthCheckTest.HealthStatusChange, which is tracked in MESOS-1802 already. > On Feb 17, 2016, at 5:21 AM, Ber

Safe update of agent attributes

sent on time. Some questions: 1. Does anyone have a good practice recommended on managing these attributes safely? 2. Has Mesos considered to fallback to old metadata if it detects incompatibility, so agents would keep running with old attributes instead of falling into crash loop? Thanks. -- Cheers, Zhitao Li

Re: Safe update of agent attributes

a change of >> attribute a "material" change for the Agent and I would avoid trying to >> recover state from previous runs; but, again, there may be perfectly >> legitimate cases in which this is desirable. >> >> -- >> *Marco Massenzio* >> http:/

Re: Downloading s3 uris

Haven't directly used s3 download, but I think a workaround (if you don't care ACL about the files) is to use http url instead. > On Feb 26, 2016, at 8:17 AM, Aaron Carey wrote: > > I'm attempti

URL for viewing persistent volumes

Hi, Is there a HTTP url to list and view existing persistent volume created so far? I'm running 0.27.1 and couldn't find how to obtain such info. Thanks! -- Cheers, Zhitao Li

Re: URL for viewing persistent volumes

ations at every slave in the cluster by examining the > master's "/slaves" endpoint. For more information, see: > > https://issues.apache.org/jira/browse/MESOS-4667 > https://reviews.apache.org/r/44047/ > > Neil > > >> On Mon, Feb 29, 2016 at 9:35 A

Re: Executors no longer inherit environment variables from the agent

es` will be set to “{}” by default. If you > do depend on the original behavior, please set > `--executor_environment_variables` flag explicitly. > > Let us know if you have any comments or concerns. > > Thanks, > Gilbert > -- Cheers, Zhitao Li

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

ist/dev/mesos/0.28.0-rc2/mesos-0.28.0.tar.gz.md5 > > > The signature of the tarball can be found at: > > > https://dist.apache.org/repos/dist/dev/mesos/0.28.0-rc2/mesos-0.28.0.tar.gz.asc > > > The PGP key used to sign the release is here: > > https://dist.apache.org/repos/dist/release/mesos/KEYS > > > The JAR is up in Maven in a staging repository here: > > https://repository.apache.org/content/repositories/orgapachemesos-1120 > > > Please vote on releasing this package as Apache Mesos 0.28.0! > > > The vote is open until Wed Mar 16 15:43:35 EDT 2016 and passes if a > majority of at least 3 +1 PMC votes are cast. > > > [ ] +1 Release this package as Apache Mesos 0.28.0 > > [ ] -1 Do not release this package because ... > > > Thanks, > -- Cheers, Zhitao Li

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

sion. By the way, could "OsTest.User" > pass in your machine? It also call "os::getgid" during test. > > On Tue, Mar 15, 2016 at 6:57 AM, Zhitao Li wrote: > >> When running `sudo make check` on debian 8, I saw the

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

ck whether this describes your issue (if so could > you close the new issue as duplicate?). Thanks! > > On Tue, Mar 15, 2016 at 6:55 AM, Zhitao Li wrote: > >> Filed https://issues.apache.org/jira/browse/MESOS-4946 to track. >> >> All "OsTest" passes under root on my m

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

his issue a blocker? Are we moving to rc3 or proceeding with 0.28.0? >> > > It was not marked as such, so I'm guessing not. @Jie and @Zhitao, can you > confirm? > > Also, we still need some binding votes for this release to go official. > @committers: can you please vote? > -- Cheers, Zhitao Li

Re: Current state of the oversubscription feature

he Mesos oversubscription >> feature [1]. In particular, I would like to know if anyone has taken a >> closer look at non-compressible resources such as memory. >> >> Anything I should be aware of? >> >> Thanks and Best Regards, >> Stephan >> >> [1] http://mesos.apache.org/documentation/latest/oversubscription/ > > > -- Cheers, Zhitao Li

State of DiscoveryInfo

Hi, Does anyone have an example of using the DiscoveryInfo from Mesos 0.22? I'm interested in understanding its current status and adoption situation, whether any real service discovery system is using it, and what's the blocker if not. Thanks. -- Cheers, Zhitao Li

How to make full version available in /version endpoint

"0.27.1" } Is there an environment variable or something which we could tweak at build/package time to get it? Thanks! -- Cheers, Zhitao Li

Re: How to make full version available in /version endpoint

on" key with an environment variable is probably sufficient for us. On Wed, Mar 23, 2016 at 4:51 PM, Vinod Kone wrote: > Not currently, no. What's your use case? > > On Wed, Mar 23, 2016 at 3:50 PM, Zhitao Li wrote: > >> Hi, >> >> Has anyone brought up the

Re: How to make full version available in /version endpoint

n with >> an environment variable doesn't seem very applicable in many environments. >> Perhaps there is a different way you could accomplish the same ultimate >> goal? >> >> >> On Wednesday, March 23, 2016, Zhitao Li wrote: >> >>> We want

Re: State of DiscoveryInfo

tml > > > http://events.linuxfoundation.org/sites/events/files/slides/mesos-networking.mesoscon2015.pdf > > > > And the design doc of DiscoveryInfo also show "Example Uses" about it: > > > https://docs.google.com/document/d/1tpnjfHsa5Joka23CqgGppqnK0jODcElBvT

Re: Persistent Volume API Change

ar from people who > are running and/or writing frameworks that make use of persistent volumes, > to see if those frameworks are setting this field properly. > > Thoughts? > > Cheers, > Greg > -- Cheers, Zhitao Li

Re: New external dependency

ironment if you don't yet have these packages installed. > > -- > ~Kevin > -- Cheers, Zhitao Li

Re: Executors no longer inherit environment variables from the agent

will no longer allow executors to inherit > > environment variables from the agent. In other words, > > `--executor_environment_variables` will be set to “{}” by default. If you > > do depend on the original behavior, please set > > `--executor_environment_variables` flag explicitly. > > > > Let us know if you have any comments or concerns. > > > > Thanks, > > Gilbert > > > -- Cheers, Zhitao Li

Re: Order of URIs in CommandInfo protobuf

ment in mesos.proto, "Any >>> URIs specified are fetched before executing the command" seems to imply >>> that ordering does not matter. I just wanted to confirm that was the case. >>> >>> Thanks, >>> Wil >>> >> >> >> > -- Cheers, Zhitao Li

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

gt; > > > > > Mesos "unified" containerizer. This support includes running > containers > > > > > > with and without filesystem isolation (i.e. running both imageless > > > > > > containers as well as containers using a docker image). Frameworks > must > > > > > > opt-in to receiving GPU resources via the GPU_RESOURCES framework > > > > > > capability (see the scarce resource problem in MESOS-5377). We > support > > > > > > 'nvidia-docker'-style docker containers by injecting a volume that > > > > > > contains the Nvidia libraries / binaries when the docker image has > > > > > > the 'com.nvidia.volumes.needed' label. Support for the docker > > > > > > containerizer will come in a future release. > > > > > > > > > > > > * [MESOS-5724] - SSL certificate validation allows for additional IP > > address > > > > subject alternative name extension verification. > > > > > > > > > > > > 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.0-rc2 > > > > > > > > > > > The candidate for Mesos 1.0.0 release is available at: > > > > > https://dist.apache.org/repos/dist/dev/mesos/1.0.0-rc2/mesos-1.0.0.tar.gz > > > > > > The tag to be voted on is 1.0.0-rc2: > > > > https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=1.0.0-rc2 > > > > > > The MD5 checksum of the tarball can be found at: > > > > > https://dist.apache.org/repos/dist/dev/mesos/1.0.0-rc2/mesos-1.0.0.tar.gz.md5 > > > > > > The signature of the tarball can be found at: > > > > > https://dist.apache.org/repos/dist/dev/mesos/1.0.0-rc2/mesos-1.0.0.tar.gz.asc > > > > > > The PGP key used to sign the release is here: > > > > https://dist.apache.org/repos/dist/release/mesos/KEYS > > > > > > The JAR is up in Maven in a staging repository here: > > > > https://repository.apache.org/content/repositories/orgapachemesos-1149 > > > > > > Please vote on releasing this package as Apache Mesos 1.0.0! > > > > > > The vote is open until Tue Jul 12 15:00:00 PDT 2016 and passes if a > > majority of at least 3 +1 PMC votes are cast. > > > > > > [ ] +1 Release this package as Apache Mesos 1.0.0 > > > > [ ] -1 Do not release this package because ... > > > > > > Thanks, > > > > Vinod > -- Cheers, Zhitao Li

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

Sorry for the confusion. > > Kapil > > On Mon, Jul 11, 2016 at 1:03 PM, Zhitao Li wrote: > > > Hi Kapil, > > > > Do you mean that the stable builds from > > http://open.mesosphere.com/downloads/mesos is using the new > configuration? > > >

Re: Enabling basic access authentication

fferent configuration I need > to set? > > Thanks! > -- Cheers, Zhitao Li

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

gt; > >> > > > >> > > * [MESOS-3094] - **Experimental** support for launching mesos > tasks > >> on > >> > > > >> > > > >> > > Windows. Note that there are no isolation guarantees provided > yet. > >> > > > >> > > > >> > > > >> > > > >> > > > >> > > * [MESOS-4090] - The `mesos.native` python module has been split > >> into > >> > > two, > >> > > > >> > > `mesos.executor` and `mesos.scheduler`. This change also removes > >> > > > >> > > > >> > > un-necessary 3rd party dependencies from `mesos.executor` and > >> > > > >> > > > >> > > `mesos.scheduler`. `mesos.native` still exists, combining both > >> > modules > >> > > for > >> > > > >> > > backwards compatibility with existing code. > >> > > > >> > > > >> > > > >> > > > >> > > > >> > > * [MESOS-1478] - Phase I of the Slave to Agent rename is complete. > >> To > >> > > support > >> > > > >> > > the rename, new duplicate flags (e.g., > >> --agent_reregister_timeout), > >> > > new > >> > > > >> > > * [MESOS-1478] - Phase I of the Slave to Agent rename is complete. > >> To > >> > > support > >> > > > >> > > the rename, new duplicate flags (e.g., > >> --agent_reregister_timeout), > >> > > new > >> > > > >> > > binaries (e.g., mesos-agent) and WebUI sandbox links have been > >> added. > >> > > All > >> > > > >> > > the logging output has been updated to use the term 'agent' now. > >> > > Flags, > >> > > > >> > > binaries and scripts with 'slave' keyword have been deprecated > >> (see > >> > > > >> > > > >> > > "Deprecations section below"). > >> > > > >> > > > >> > > > >> > > > >> > > > >> > > * [MESOS-4312] - **Experimental** support for building and running > >> > mesos > >> > > on > >> > > > >> > > IBM PowerPC platform. > >> > > > >> > > > >> > > > >> > > > >> > > > >> > > * [MESOS-4189] - Weights for resource roles can now be configured > >> > > dynamically > >> > > > >> > > via the new '/weights' endpoint on the master. > >> > > > >> > > > >> > > > >> > > > >> > > > >> > > * [MESOS-4424] - Support for using Nvidia GPUs as a resource in > the > >> > > > >> > > > >> > > Mesos "unified" containerizer. This support includes running > >> > > containers > >> > > > >> > > with and without filesystem isolation (i.e. running both > imageless > >> > > > >> > > > >> > > containers as well as containers using a docker image). > Frameworks > >> > > must > >> > > > >> > > opt-in to receiving GPU resources via the GPU_RESOURCES > framework > >> > > > >> > > > >> > > capability (see the scarce resource problem in MESOS-5377). We > >> > > support > >> > > > >> > > 'nvidia-docker'-style docker containers by injecting a volume > that > >> > > > >> > > > >> > > contains the Nvidia libraries / binaries when the docker image > has > >> > > > >> > > > >> > > the 'com.nvidia.volumes.needed' label. Support for the docker > >> > > > >> > > > >> > > containerizer will come in a future release. > >> > > > >> > > > >> > > > >> > > * [MESOS-5724] - SSL certificate validation allows for additional > IP > >> > > address > >> > > > >> > > subject alternative name extension verification. > >> > > > >> > > 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.0-rc4 > >> > > > >> > > > >> > > > >> > > >> > > >> > > > >> > > > >> > > The candidate for Mesos 1.0.0 release is available at: > >> > > > >> > > > >> > > >> > https://dist.apache.org/repos/dist/dev/mesos/1.0.0-rc4/mesos-1.0.0.tar.gz > >> > > > >> > > > >> > > The tag to be voted on is 1.0.0-rc4: > >> > > > >> > > > >> > https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=1.0.0-rc4 > >> > > > >> > > > >> > > The MD5 checksum of the tarball can be found at: > >> > > > >> > > > >> > > > >> > > >> > https://dist.apache.org/repos/dist/dev/mesos/1.0.0-rc4/mesos-1.0.0.tar.gz.md5 > >> > > > >> > > > >> > > The signature of the tarball can be found at: > >> > > > >> > > > >> > > > >> > > >> > https://dist.apache.org/repos/dist/dev/mesos/1.0.0-rc4/mesos-1.0.0.tar.gz.asc > >> > > > >> > > > >> > > The PGP key used to sign the release is here: > >> > > > >> > > https://dist.apache.org/repos/dist/release/mesos/KEYS > >> > > > >> > > > >> > > The JAR is up in Maven in a staging repository here: > >> > > > >> > > > >> https://repository.apache.org/content/repositories/orgapachemesos-1153 > >> > > > >> > > > >> > > Please vote on releasing this package as Apache Mesos 1.0.0! > >> > > > >> > > > >> > > [ ] +1 Release this package as Apache Mesos 1.0.0 > >> > > > >> > > [ ] -1 Do not release this package because ... > >> > > > >> > > > >> > > Thanks, > >> > > > >> > > >> > >> > >> > >> -- > >> Best Regards, > >> Haosdent Huang > >> > > > > > -- Cheers, Zhitao Li

Re: [Mesos 2.0] Let's talk about the future

u could either share your ideas or vote on > these items, and we will discuss it in next community sync. > > We may not have an unshakeable conclusion as container technology is > evolving at an ever faster pace, but the whole community, especially > newbies like myself, would profoundly benefit from a clear plan and > priority for next 3-6 months. > > Cheers, > /Jay > > > -- Cheers, Zhitao Li

Re: Using mesos' cfs limits on a docker container?

t the memory >>>> limitations. Is there any way to mix these two methods of isolation? I'd >>>> like my executor/algorithm to run inside a docker container, but have that >>>> container's memory and cpu usage controlled by systemd/mesos. >>>> >>>> >>>> >>>> Thanks, >>>> >>>> Mark >>>> -- >>>> >>>> Mark Hammons - +33 06 03 69 56 56 >>>> >>>> Research Engineer @ BioEmergences >>>> <https://urldefense.proofpoint.com/v2/url?u=http-3A__bioemergences.iscpif.fr&d=DQMFaQ&c=LNdz7nrxyGFUIUTz2qIULQ&r=cPg4mUupZEtURFK34GyDCtRjHoUmKrI7oHRZqAh3hZY&m=p3yjpxMelmcew1dQtqJniCFVDpbSbJQBXaW-mA1QVHU&s=hlyM8jpFaEkcQ5X8UJs0BTG53J2X6F-zEs0JIKxCFEQ&e=> >>>> >>>> Lab Phone: 01 69 82 34 19 >>>> >>> >>> -- Cheers, Zhitao Li

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

t >>> ;h=1.0.1-rc1 >>> >> >>> >> >>> >> The MD5 checksum of the tarball can be found at: >>> >> >>> >> https://dist.apache.org/repos/dist/dev/mesos/1.0.1-rc1/mesos >>> >> -1.0.1.tar.gz.md5 >>> >> >>> >> >>> >> The signature of the tarball can be found at: >>> >> >>> >> https://dist.apache.org/repos/dist/dev/mesos/1.0.1-rc1/mesos >>> >> -1.0.1.tar.gz.asc >>> >> >>> >> >>> >> The PGP key used to sign the release is here: >>> >> >>> >> https://dist.apache.org/repos/dist/release/mesos/KEYS >>> >> >>> >> >>> >> The JAR is up in Maven in a staging repository here: >>> >> >>> >> https://repository.apache.org/content/repositories/orgapache >>> mesos-1155 >>> >> >>> >> >>> >> Please vote on releasing this package as Apache Mesos 1.0.1! >>> >> >>> >> >>> >> The vote is open until Mon Aug 15 17:29:33 PDT 2016 and passes if a >>> >> majority of at least 3 +1 PMC votes are cast. >>> >> >>> >> >>> >> [ ] +1 Release this package as Apache Mesos 1.0.1 >>> >> >>> >> [ ] -1 Do not release this package because ... >>> >> >>> >> >>> >> Thanks, >>> >> >>> > >>> > >>> >> >> > > > -- > Best Regards, > Haosdent Huang > > > -- Cheers, Zhitao Li

Re: How many roles are we supported?

On Wed, Sep 7, 2016 at 11:35 AM Klaus Ma wrote: > >> + user@ >> >> >> On Wed, Sep 7, 2016 at 11:31 AM Klaus Ma wrote: >> >>> IMO, it does not make sense to let user to try it :). It's better for us >>> (Mesos Dev) to provide suggestion :)

Re: Non-checkpointing frameworks

gt;> >> >>> >> Checkpointing is not currently the default, but in my experience it is >>> >> often enabled for production frameworks. As part of the work on >>> >> supporting partition-aware Mesos frameworks (see MESOS-4049), we are >>> >> considering: >>> >> >>> >> (a) requiring that partition-aware frameworks must also enable >>> >> checkpointing, and/or >>> >> (b) enabling checkpointing by default >>> >> >>> >> If you have intentionally decided to disable checkpointing for your >>> >> Mesos framework, I'd be curious to hear more about your use-case and >>> >> why you haven't enabled it. >>> >> >>> >> Thanks! >>> >> >>> >> Neil >>> >> >>> >> -- >>> >> Zameer Manji >>> >> >>> > >>> >> >> > -- Cheers, Zhitao Li

Re: Performance regression in v1 api vs v0

>> BENCHMARK_Test.SchedulerDriver/1 >>>>> Reconciling 1 tasks took 316.115078ms using the scheduler driver >>>>> [ OK ] Tasks/SchedulerReconcileTasks_ >>>>> BENCHMARK_Test.SchedulerDriver/1 (385 ms) >>>>> [ RUN ] Tasks/SchedulerReconcileTasks_ >>>>> BENCHMARK_Test.SchedulerDriver/2 >>>>> Reconciling 5 tasks took 1.239050154secs using the scheduler driver >>>>> [ OK ] Tasks/SchedulerReconcileTasks_ >>>>> BENCHMARK_Test.SchedulerDriver/2 (1379 ms) >>>>> [ RUN ] Tasks/SchedulerReconcileTasks_ >>>>> BENCHMARK_Test.SchedulerDriver/3 >>>>> Reconciling 10 tasks took 2.38445672secs using the scheduler driver >>>>> [ OK ] Tasks/SchedulerReconcileTasks_ >>>>> BENCHMARK_Test.SchedulerDriver/3 (2711 ms) >>>>> ``` >>>>> >>>>> *SchedulerLibrary* is the HTTP API, *SchedulerDriver* is the old way >>>>> based on libmesos.so. >>>>> >>>>> On Sun, Oct 16, 2016 at 2:41 PM, Dario Rexin wrote: >>>>> >>>>>> Hi all, >>>>>> >>>>>> I recently did some performance testing on the v1 scheduler API and >>>>>> found that throughput is around 10x lower than for the v0 API. Using 1 >>>>>> connection, I don’t get a lot more than 1,500 calls per second, where the >>>>>> v0 API can do ~15,000. If I use multiple connections, throughput maxes >>>>>> out >>>>>> at 3 connections and ~2,500 calls / s. If I add any more connections, the >>>>>> throughput per connection drops and the total throughput stays around >>>>>> ~2,500 calls / s. Has anyone done performance testing on the v1 API >>>>>> before? >>>>>> It seems a little strange to me, that it’s so much slower, given that the >>>>>> v0 API also uses HTTP (well, more or less). I would be thankful for any >>>>>> comments and experience reports of other users. >>>>>> >>>>>> Thanks, >>>>>> Dario >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Best Regards, >>>>> Haosdent Huang >>>>> >>>>> >>>>> >>>> >>>> >>> >>> >>> -- >>> Deshi Xiao >>> Twitter: xds2000 >>> E-mail: xiaods(AT)gmail.com >>> >> >> >> >> -- >> Anand Mazumdar >> >> >> > -- Cheers, Zhitao Li

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

>> The candidate for Mesos 1.1.0 release is available at: >> https://dist.apache.org/repos/dist/dev/mesos/1.1.0-rc1/mesos-1.1.0.tar.gz >> >> The tag to be voted on is 1.1.0-rc1: >> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=1.1.0-rc1 >> >> The MD5 checksum of the tarball can be found at: >> https://dist.apache.org/repos/dist/dev/mesos/1.1.0-rc1/mesos >> -1.1.0.tar.gz.md5 >> >> The signature of the tarball can be found at: >> https://dist.apache.org/repos/dist/dev/mesos/1.1.0-rc1/mesos >> -1.1.0.tar.gz.asc >> >> The PGP key used to sign the release is here: >> https://dist.apache.org/repos/dist/release/mesos/KEYS >> >> The JAR is up in Maven in a staging repository here: >> https://repository.apache.org/content/repositories/orgapachemesos-1158 >> >> Please vote on releasing this package as Apache Mesos 1.1.0! >> >> The vote is open until Fri Oct 21 21:57:02 CEST 2016 and passes if a >> majority of at least 3 +1 PMC votes are cast. >> >> [ ] +1 Release this package as Apache Mesos 1.1.0 >> [ ] -1 Do not release this package because ... >> >> Thanks, >> Alex & Till >> >> > -- Cheers, Zhitao Li

Re: mesos cpuset isolator module available

t out, have issues, or want to make improvements, please >>> post to github - I've done some very simple/trivial testing. >>> >>> Chris >>> >> >> >> >> -- >> Deshi Xiao >> Twitter: xds2000 >> E-mail: xiaods(AT)gmail.com >> > > -- Cheers, Zhitao Li

Re: Welcome Haosdent Huang as Mesos Committer and PMC member!

s.google.com/document/d/1wq-M4KoMOJWZTNTN- > hvy-H8ZGLXG6CF9VP2IY_UU5_0/edit?ts=57e0029d> > for your perusal. > > Thanks, > Vinod > > P.S: Sorry for the delay in sending the welcome email. > -- Cheers, Zhitao Li

Structured logging for Mesos (or c++ glog)

e has brought the conversation of making Mesos logs easier to process, or if anyone has experience to share. Thanks! -- Cheers, Zhitao Li

Re: Structured logging for Mesos (or c++ glog)

le in such use cases. On Mon, Dec 19, 2016 at 9:58 AM, James Peach wrote: > > > On Dec 19, 2016, at 9:43 AM, Zhitao Li wrote: > > > > Hi, > > > > I'm looking at how to better utilize ElasticSearch to perform log > analysis for logs from Mesos. It seems li

Re: Structured logging for Mesos (or c++ glog)

enough for your use case though. > > — > *Joris Van Remoortere* > Mesosphere > > On Mon, Dec 19, 2016 at 9:58 AM, James Peach wrote: > > > > > > On Dec 19, 2016, at 9:43 AM, Zhitao Li wrote: > > > > > > Hi, > > > > > > I'

Re: Structured logging for Mesos (or c++ glog)

ough. > > > > — > > *Joris Van Remoortere* > > Mesosphere > > > > On Mon, Dec 19, 2016 at 9:58 AM, James Peach wrote: > > > > > > > On Dec 19, 2016, at 9:43 AM, Zhitao Li wrote: > > > > > > Hi, > > > > > >

Re: Structured logging for Mesos (or c++ glog)

, 2016 at 3:25 PM, James Peach wrote: > > > On Dec 19, 2016, at 2:54 PM, Zhitao Li wrote: > > > > Hi James, > > > > Stitching events together is only one possible use cases, and I'm not > exactly sure what you meant by directly event logging. > > > &

Re: Structured logging for Mesos (or c++ glog)

in Dockerized deployments, as part of this Docker > agent <https://sematext.com/docker/>. One could also use Logstash for > parsing/structuring, but Logstash is a bit heavy. > > I hope this helps. > > Otis > -- > Monitoring - Log Management - Alerting - Anomaly Detectio

Re: Optimize libprocess performance

ive_mutex firewall_mutex;* > > > > In particular, everytime event enqueue/dequeue both need to get lock, > > maybe use lookfree struct is better. > > > > > > > > If have any optimize suggestion or discussion, please let me know, > thanks. > > > > > > > > [image: cid:image001.png@01D0E8C5.8D08F440] > > > > > > > > Bingqiang Pang(庞兵强) > > > > > > > > Distributed and Parallel Software Lab > > > > Huawei Technologies Co., Ltd. > > > > Email:pangbingqi...@huawei.com > > > > > > > > > > > -- Cheers, Zhitao Li

Proposal for evaluating Mesos scalability and robustness through stress test.

gt;. Please feel free to provide your suggestions and feedback through comment on the draft. Probably many of you have similar questions as we have. We will be happy to share our findings in these experiments with the Mesos community. Please stay tuned. -- Cheers, Ao Ma & Zhitao Li

Re: Providing end-user feedback on Docker image download progress

s large Docker images via the > >>> Mesos Containerizer and we like to know what our options are of adding > >>> this feature either to the framework, to a Mesos module, or to Mesos > >>> itself using some sort of API or a new task state next to STAGING like > >>> DOWNLOADING including detailed progress information. > >>> > >>> We want to contribute this work back to the project and like to know > >>> which of the above and other options are the most viable. > >>> > >>> Cheers, > >>> > >>> Frank > >> > >> > -- Cheers, Zhitao Li

Plan for upgrading protobuf==3.2.0 in Mesos

ience around updating the protobuf dependency, so please let us know if you have any concern or further questions. -- Cheers, Zhitao Li and Anand Mazumdar,

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

an important role >> organizing >> > > MesosCon Asia last year and this year! >> > > >> > > His formal committer checklist can be found here: >> > > https://docs.google.com/document/d/1iSiqmtdX_0CU-YgpViA6r6PU_ >> > aMCVuxuNUZ458FR7Qw/edit?usp=sharing >> > > >> > > Welcome, Gilbert! >> > > >> > > - Jie >> > >> > > -- Cheers, Zhitao Li

Re: Welcome Greg Mann as a new committer and PMC member!

te a > > few moving parts. Additionally, he also worked on improving the scheduler > > and executor APIs. > > > > Here is his more formal checklist for your perusal. > > > > https://docs.google.com/document/d/1S6U5OFVrl7ySmpJsfD4fJ3_ > > R8JYRRc5spV0yKrpsGBw/edit > > > > Thanks, > > Vinod > > > > > -- Cheers, Zhitao Li

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

passes if a > majority of at least 3 +1 PMC votes are cast. > > [ ] +1 Release this package as Apache Mesos 1.4.0 > [ ] -1 Do not release this package because ... > > Thanks, > Anand and Kapil > > -- Cheers, Zhitao Li

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

s >>> eager to help folks in the community and he has been helping with a lot of >>> Mesos reviews as well. >>> >>> Here is his formal committer candidate checklist: >>> >>> https://docs.google.com/document/d/19G5zSxhrRBdS6GXn9KjCznjX >>> 3cp0mUbck6Jy1Hgn3RY/edit?usp=sharing >>> <https://docs.google.com/document/d/19G5zSxhrRBdS6GXn9KjCznjX3cp0mUbck6Jy1Hgn3RY/edit?usp=sharing> >>> >>> Congrats James! >>> >>> Yan >>> >>> >> >> >> -- >> Deshi Xiao >> Twitter: xds2000 >> E-mail: xiaods(AT)gmail.com >> > > -- Cheers, Zhitao Li

Re: Updating running tasks in-place

279> > (which >is captured in another JIRA) - Certain metadata, e.g., labels (but I imagine not all metadata makes >equal sense to be updatable). > > What other/specific use cases are folks interested in? > > Best, > Yan > -- Cheers, Zhitao Li

Re: Subscribe to an active framework through HTTP API Scheduler

s message is private and confidential. If you have received this > message in error, please notify the sender or serviced...@piksel.com and > remove it from your system. > > Piksel Inc is a company registered in the United States, 2100 Powers > Ferry Road SE, Suite 400, Atlanta, GA 30339 > <https://maps.google.com/?q=2100+Powers+Ferry+Road+SE,+Suite+400,+Atlanta,+GA+30339&entry=gmail&source=g> > -- Cheers, Zhitao Li

Re: Welcome Andrew Schwartzmeyer as a new committer and PMC member!

ws. > > Here is his committer candidate checklist for your perusal: > https://docs.google.com/document/d/1MfJRYbxxoX2-A- > g8NEeryUdUi7FvIoNcdUbDbGguH1c/ > > Congrats Andy! > ~Joseph > -- Cheers, Zhitao Li

Duplicate task ID for same framework on different agents

<https://issues.apache.org/jira/browse/MESOS-8353> to track this potential bug. Thanks! -- Cheers, Zhitao Li

Re: Questions about Pods and the Mesos Containerizer

t;>Is there any performance data about using the Mesos containeriser >>with container images versus using the Docker containeriser? >>- >> >> how does the Mesos containerizer handle extremely large images? >> - >> >> how does the Mesos containerizer handle dozens/hundreds of >> concurrent pulls? >> >> >> If anyone has had any experience using the UCR and/or pods with the sort >> of workflow we’re considering, your input would be highly useful! >> >> Cheers, >> >> David Morrison >> >> Software Engineer @ Yelp >> >> > -- Cheers, Zhitao Li

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

/orgapachemesos-1222 > > > > Please vote on releasing this package as Apache Mesos 1.5.0! > > > > The vote is open until Tue Feb 6 17:35:16 PST 2018 and passes if a > > majority of at least 3 +1 PMC votes are cast. > > > > [ ] +1 Release this package as Apache Mesos 1.5.0 > > [ ] -1 Do not release this package because ... > > > > Thanks, > > Jie and Gilbert > > > -- Cheers, Zhitao Li

Re: Get leading master from zookeeper

there are json.info_.. MasterInfo jsons available in zk, but how can I > translate this to figure out the leading master at any given point in time? > > Regards, > Ajay > -- Cheers, Zhitao Li

Re: Welcome Chun-Hung Hsiao as Mesos Committer and PMC Member

, insightful, and > >> opinionated. I am confident that he will be a great addition to our > >> committer pool. Thanks Chun for all your contributions to the project so > >> far! > >> > >> His committer checklist can be found here: > >> https://docs.google.com/document/d/1FjroAvjGa5NdP29zM7-2eg6t > >> LPAzQRMUmCorytdEI_U/edit?usp=sharing > >> > >> - Jie > >> > > > > > -- Cheers, Zhitao Li

Re: Release policy and 1.6 release schedule

le. > > I'm curious to hear people's thoughts on this, developers and users alike! > > Cheers, > Greg > > > [1] https://docs.google.com/document/d/1JrF7pA6gcBZ6iyeP5YgD > G62ifn0cZIBWw1f_Ler6fLM/edit# > [2] http://mesos.apache.org/documentation/latest/versioning/ > #release-schedule > -- Cheers, Zhitao Li

Support deadline for tasks

Thanks! -- Cheers, Zhitao Li

Re: Support deadline for tasks

Thanks James. I'll update the JIRA with our names and start with some prototype. On Thu, Mar 22, 2018 at 9:07 PM, James Peach wrote: > > > > On Mar 22, 2018, at 10:06 AM, Zhitao Li wrote: > > > > In our environment, we run a lot of batch jobs, some of which have t

Reason of cascaded kill in a group

f this reason? If not, we probably can just change the reason without a opt-in mechanism from framework (i.e, a new framework capability). Please let me know if your framework as such a dependency. Thanks! -- Cheers, Zhitao Li

Re: Reason of cascaded kill in a group

ot exist is > safe from a backwards compatibility perspective. > > On Mon, Apr 9, 2018 at 10:32 AM, Zhitao Li wrote: > >> Hi, >> >> We are considering adding a new reason to StatusUpdate::Reason >> <https://github.com/apache/mesos/blob/master/include/mesos/mesos.p

Questions about secret handling in Mesos

Hello, We at Uber plan to use volume/secret isolator to send secrets from Uber framework to Mesos agent. For this purpose, we are referring to these documents: - File based secrets design doc and sl

Re: Questions about secret handling in Mesos

SWORD=test_password … > ``` > > > On 19. Apr 2018, at 19:57, Zhitao Li wrote: > > Hello, > > We at Uber plan to use volume/secret isolator to send secrets from Uber > framework to Mesos agent. > > For this purpose, we are referring to these documents: > >

Re: mesos-slave Failed to initialize: Failed to bind on 0.0.0.0:0: Address already in use: Address already in use [98]

/run/docker.sock > unix 2 [ ACC ] STREAM LISTENING 178252401 > 27855/docker-contai /var/run/docker/libcontainerd/docker-containerd.sock > unix 2 [ ACC ] STREAM LISTENING 145571282/nscd > /var/run/nscd/socket > unix 2 [ ACC ] STREAM LISTENING 178252469 27819/dockerd > /run/docker/libnetwork/2dc9ef136eb6933a5634dcf439d9fb > d4acf96a5de16eb79122b6ddd8aefcf81c.sock > unix 2 [ ACC ] STREAM LISTENING 178253543 28184/node > /root/.forever/sock/worker.1524559297488oBZ.sock > unix 2 [ ACC ] STREAM LISTENING 159081424/AliYunDun > /usr/local/aegis/Aegis- > unix 2 [ ACC ] SEQPACKET LISTENING 8173 > 416/systemd-udevd /run/udev/control > > So where is the problem? Thanks. > -- Cheers, Zhitao Li

Re: Questions about secret handling in Mesos

tobuf to JSON conversion for our API endpoints and I don't > think we do any special case logic for `Secret` type in that conversion. So > `value` based secrets will have their value show up in v1 (and likely v0) > API endpoints. > > On Mon, Apr 23, 2018 at 9:25 AM, Zhitao Li wrote:

Re: narrowing task sandbox permissions

Sorry for getting back to this really late, but we got bit by this behavior change in our environment. The broken scenario we had: 1. We are using Aurora to launch docker containerizer based tasks on Mesos; 2. Most of our docker containers had some legacy behavior: *the execution ente

Re: narrowing task sandbox permissions

Adding James directly. On Fri, Jun 15, 2018 at 11:06 AM Zhitao Li wrote: > Sorry for getting back to this really late, but we got bit by this > behavior change in our environment. > > The broken scenario we had: > >1. We are using Aurora to launch docker containeri

Support image and resource pre-fetching in Mesos

g services. Before delving into detailed proposal, I wonder if anyone has done similar things or has similar requirements. Thanks! -- Cheers, Zhitao Li

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

;>>> >>> https://dist.apache.org/repos/dist/dev/mesos/1.6.1-rc1/mesos-1.6.1.tar.gz >>> >>>> >>> >>>> The tag to be voted on is 1.6.1-rc1: >>> >>>> >>> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=commit;h=1.6.1-rc1 >>> >>>> >>> >>>> The SHA512 checksum of the tarball can be found at: >>> >>>> >>> >>>> >>> https://dist.apache.org/repos/dist/dev/mesos/1.6.1-rc1/mesos-1.6.1.tar.gz.sha512 >>> >>>> >>> >>>> The signature of the tarball can be found at: >>> >>>> >>> >>>> >>> https://dist.apache.org/repos/dist/dev/mesos/1.6.1-rc1/mesos-1.6.1.tar.gz.asc >>> >>>> >>> >>>> The PGP key used to sign the release is here: >>> >>>> https://dist.apache.org/repos/dist/release/mesos/KEYS >>> >>>> >>> >>>> The JAR is in a staging repository here: >>> >>>> >>> https://repository.apache.org/content/repositories/orgapachemesos-1229 >>> >>>> >>> >>>> Please vote on releasing this package as Apache Mesos 1.6.1! >>> >>>> >>> >>>> The vote is open until Fri Jun 29 18:46:28 PDT 2018 and passes if a >>> >>>> majority of at least 3 +1 PMC votes are cast. >>> >>>> >>> >>>> [ ] +1 Release this package as Apache Mesos 1.6.1 >>> >>>> [ ] -1 Do not release this package because ... >>> >>>> >>> >>>> Thanks, >>> >>>> Greg >>> >>>> >>> >>> >>> >>> >>> > >>> >> >> > -- Cheers, Zhitao Li

Re: [VOTE] Move the project repos to gitbox

ot;mesos", "mesos-site") from > the "git-wip" git server to the new "gitbox" server to better avail GitHub > integrations. > > > > Please vote +1, 0, -1 regarding the move to gitbox. The vote will close > in 3 business days. > > > +1 -- Cheers, Zhitao Li

Re: Operations Working Group - First Meeting

Please count me on. Looking forward to it. Sent from my iPhone > On Jul 20, 2018, at 4:05 PM, Gastón Kleiman wrote: > > Hi Abel, > > I would love to learn more from people operating Mesos clusters of any > size. We can discuss what is working great, what is on the roadmap, and > what could be

Re: Welcome Meng Zhu as PMC member and committer!

Congratulations! On Sun, Nov 11, 2018, 7:26 PM Jason Lai Congrats, Meng! > > On Mon, Nov 5, 2018 at 9:54 AM Benno Evers wrote: > >> Congratulations, Meng! >> >> On Thu, Nov 1, 2018 at 9:54 AM Yan Xu wrote: >> >>> Congratulations! >>> >>> >>> On Wed, Oct 31, 2018 at 4:50 PM Vinod Kone wrote: >>