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: [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: RFC: update C++ style to require the "override" keyword

ng-tidy` could inform what flags should have been added (there are some > missing features in the cmake build though, e.g., some isolators which > would > have benefited from `override` recently). > > > Cheers, > > Benjamin > > -- Cheers, Zhitao Li

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

ps://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

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: 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 contain

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

Follow up on instructions on CMake and VSCode support

Hi Andrew, I remembered that you gave an pretty exciting talk about setting up CMake and VSCode to parse Mesos code base. I'm quite curious on setting that up myself. Can you share any instructions/notes about that? Thanks! -- Cheers, Zhitao Li

Re: [mesos-mail] Re: [Performance WG] Notes from meeting today

t; > > > > > > (2) Kapil discussed benchmarks for the long standing "offer > starvation" > > > > issue: > > > > > > > > https://issues.apache.org/jira/browse/MESOS-3202 > > > > > > > > I'll send out an email or document soon with some background on this > > > issue > > > > as well as our options to address it. > > > > > > > > Let me know if you have any questions or feedback! > > > > > > > > Ben > > > > > > -- > > > You received this message because you are subscribed to the Google > Groups > > > "Apache Mesos Mail Lists" group. > > > Visit this group at > > https://groups.google.com/a/mesosphere.io/group/mesos- > > > mail/. > > > For more options, visit > > https://groups.google.com/a/mesosphere.io/d/optout > > > . > > > > > > -- Cheers, Zhitao Li

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

t; Docker failures > >>> * Support for jemalloc on Linux > >>> > >>> 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.6.0-rc1 > >>> > >>> > >>> > >>> The candidate for Mesos 1.6.0 release is available at: > >>> https://dist.apache.org/repos/dist/dev/mesos/1.6.0-rc1/mesos > >> -1.6.0.tar.gz > >>> > >>> The tag to be voted on is 1.6.0-rc1: > >>> https://git-wip-us.apache.org/repos/asf?p=mesos.git;a= > commit;h=1.6.0-rc1 > >>> > >>> The SHA512 checksum of the tarball can be found at: > >>> https://dist.apache.org/repos/dist/dev/mesos/1.6.0-rc1/ > >>> mesos-1.6.0.tar.gz.sha512 > >>> > >>> The signature of the tarball can be found at: > >>> https://dist.apache.org/repos/dist/dev/mesos/1.6.0-rc1/ > >>> mesos-1.6.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 in a staging repository here: > >>> https://repository.apache.org/content/repositories/orgapachemesos-1223 > >>> > >>> Please vote on releasing this package as Apache Mesos 1.6.0! > >>> > >>> The vote is open until Thu May 10 20:45:34 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.0 > >>> [ ] -1 Do not release this package because ... > >>> > >>> Thanks, > >>> Greg > >>> > >> > > -- Cheers, Zhitao Li

Re: Follow up on providing `--reconfiguration_policy=any` in future versions

sue. > > Best regards, > Benno > > On Tue, Feb 20, 2018 at 7:47 PM, Zhitao Li <zhitaoli...@gmail.com> wrote: > > > Hi Benno, > > > > Thanks for the the diff. I took a quick look and cannot anticipate issues > > with it in our environment. I'll talk to our

Re: Reconsidering `allocatable` check in the allocator

e are about to offer some of the resources from a particular > agent, > > why > > >> would we filter anything at all? I doubt we should be concerned about > > the > > >> size of the offer representation travelling through the network. If > > >> available resources are "cpus:0.001,gpus:1" and we want to allocate > GPU, > > >> what is the benefit of filtering CPU? > > >> > > >> What about the following: > > >> allocatable(R) > > >> { > > >> return true > > >> iff (there exists r in R for which size(r) > MIN(type(r))) > > >> } > > > > > > I think this is less about communication overhead, but more a tool to > > help to make sure that offered resources are actually useful to > frameworks. > > > > I don't know whether there's a JIRA for this, but in the past we've > > proposed the idea of schedulers suppressing or filtering offers with a > > minimum resources specification, i.e. "don't bother me with offers that > > aren't at least X" > > > > J > -- Cheers, Zhitao Li

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

Re: API review: max_duration on TaskInfo

A quick update: James and I think the name `max_completion_time` is a bit better than `max_duration`. Semantic should remain the same. On Mon, Mar 26, 2018 at 9:52 AM, Zhitao Li <zhitaoli...@gmail.com> wrote: > Hi Benjamin, > > James and I did some quick search about some exist

Re: API review: max_duration on TaskInfo

24.shtml > > I didn't see it in any other systems I looked at either, with people > suggesting wrapping commands with the 'timeout' command. I suspect most > systems have the user do this on their own with a simple timeout wrapper > script? > > On Fri, Mar 23, 2018 at 2:21 PM, Zhi

API review: max_duration on TaskInfo

could suffer from clock skews, so same absolute deadline would result in inconsistent behavior; - Framework can just trivially translate its own clock as source of truth to translate absolute deadline to current time + max_duration. Please let me know what you think. Thanks. -- Cheers,

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 <jpe...@apache.org> wrote: > > > > On Mar 22, 2018, at 10:06 AM, Zhitao Li <zhitaoli...@gmail.com> wrote: > > > > In our environme

Support deadline for tasks

Thanks! -- Cheers, Zhitao Li

API Review: Resize (persistent) volume support

/docs/csi.md -- Cheers, Zhitao Li

Question on status update retry in agent

ce or for each unacknowledged status update? I'll study the code in status update manager and agent separately but some official answer will definitely help. Many thanks! -- Cheers, Zhitao Li

Re: Release policy and 1.6 release schedule

gt; > 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

Re: API Review Policy

://docs.google.com/document/d/1JrF7pA6gcBZ6iyeP5YgDG62ifn0cZ > IBWw1f_Ler6fLM/edit > [2] https://cwiki.apache.org/confluence/display/TS/API+Review+Process > -- Cheers, Zhitao Li

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

ble, but also intelligent, 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: Looking for a shepherd for MESOS-4965

com> wrote: > Zhitao, I can provide some feedback because it most likely overlap with the > Resource Provider/CSI work. > > - Jie > > On Fri, Mar 2, 2018 at 9:08 PM, Zhitao Li <zhitaoli...@gmail.com> wrote: > > > Hi, > > > > As our workload using pers

Looking for a shepherd for MESOS-4965

tation. Thanks! -- Cheers, Zhitao Li

Re: Surfacing additional issues on agent host to schedulers

Hi Avinash, Sorry for the slow response. On Wed, Feb 21, 2018 at 11:50 AM, Avinash Sridharan <avin...@mesosphere.io> wrote: > On Wed, Feb 21, 2018 at 11:18 AM, Zhitao Li <zhitaoli...@gmail.com> wrote: > > > Hi Avinash, > > > > We use haproxy of all outgoi

Re: Feb 21 Performance WG Meeting Canceled

Hi folks, since there's nothing on the agenda for this month's meeting. I > will cancel it and plan to meet next month. If there are any topics folks > would like to discuss let me know and we can schedule one sooner! > -- Cheers, Zhitao Li

Re: Surfacing additional issues on agent host to schedulers

or...@gmail.com> wrote: > > > > > > On Feb 20, 2018, at 11:11 AM, Zhitao Li <zhitaoli...@gmail.com> wrote: > > > > > > Hi, > > > > > > In one of recent Mesos meet up, quite a couple of cluster operators had > > >

Re: Surfacing additional issues on agent host to schedulers

e provided list? On Tue, Feb 20, 2018 at 3:54 PM, James Peach <jor...@gmail.com> wrote: > > > On Feb 20, 2018, at 11:11 AM, Zhitao Li <zhitaoli...@gmail.com> wrote: > > > > Hi, > > > > In one of recent Mesos meet up, quite a couple of cluster operator

Surfacing additional issues on agent host to schedulers

d. Thanks! -- Cheers, Zhitao Li

Re: Follow up on providing `--reconfiguration_policy=any` in future versions

issues. > > Of course, I'm also up for a follow-up meeting. > > Best regards, > Benno > > > On Thu, Feb 15, 2018 at 9:03 PM, Zhitao Li <zhitaoli...@gmail.com> wrote: > > > Hi Vinod/Benno, > > > > This is a follow up from MESOS-1739. We have recently

Follow up on providing `--reconfiguration_policy=any` in future versions

lp our operation. Do we want to have a follow up meeting to see what's blockers to fully implement that? Thanks. -- Cheers, Zhitao Li

Re: [VOTE] C++14 Upgrade

On Mon, Feb 12, 2018 at 11:58 AM, Michael Park <mp...@apache.org> wrote: > On Mon, Feb 12, 2018 at 10:32 AM, Zhitao Li <zhitaoli...@gmail.com> wrote: > > > Will there be a deprecation cycle for the proposed change? > > > There is no deprecation cycle f

Re: [VOTE] C++14 Upgrade

d in MESOS-7949 > > <https://issues.apache.org/jira/browse/MESOS-7949> are: > > > > - Generic lambdas > > - New lambda captures (Proper move captures!) > > - SFINAE result_of (We can remove stout/result_of.hpp) > > - Variable templates > > - Relaxed constexpr functions > > - Simple utilities such as std::make_unique > > - Metaprogramming facilities such as decay_t, index_sequence > > Are these all internal though? Maybe move captures could yield some > performance improvements? > > -- Cheers, Zhitao Li

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

ere: > > https://repository.apache.org/content/repositories/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: API working group

Yes I’m interested in attending. > On Jan 30, 2018, at 10:42 AM, Vinod Kone wrote: > > Hi folks, > > We've had good success with our containerization, performance and community > working groups and so we would like to keep the momentum going and spin up > new WGs as

Re: Sharing master detector to modules

OS overlay. > > On Tue, Jan 16, 2018 at 10:20 AM, Zhitao Li <zhitaoli...@gmail.com> wrote: > > > Hi, > > > > Some of our future development work on our custom modules requires them > to > > know the current leader of Mesos master. While it seems like

Sharing master detector to modules

to share the existing detector instance in slave to the module. Any comment on this idea? Thanks. -- 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: Customize executor_registration_timeout per executor

Not yet. I can put it on the agenda after holiday season. On Thu, Dec 14, 2017 at 5:44 PM, Benjamin Mahler <bmah...@apache.org> wrote: > Have you brought this up in the containerization working group? > > On Tue, Dec 12, 2017 at 9:48 AM, Zhitao Li <zhitaoli...@gmail.com>

Implicit reconcile "pauses" offer stream in large cluster

't see any issue when processing it this way. Thanks! -- Cheers, Zhitao Li

Re: Container launch metrics on agent

ems like `container_launch_errors ` is only incremented in Slave::executorLaunched, so standalone container errors are not tracked by this metric either. > > On Fri, Dec 1, 2017 at 9:34 AM, Zhitao Li <zhitaoli...@gmail.com> wrote: > > > Hi, > > > > We are working

Re: Customize executor_registration_timeout per executor

t; > > > On Dec 11, 2017, at 8:55 AM, Zhitao Li <zhitaoli...@gmail.com> wrote: > > > > > > Hi, > > > > > > We are running tasks which has very large docker images and tasks which > > use > > > much smaller images in our clusters, The

Customize executor_registration_timeout per executor

executor specific parameter to make this customizable per executor, instead of one single value per agent. Thanks! -- Cheers, Zhitao Li

Re: Agent reconfiguration without losing tasks

hese requirements, I would encourage you to apply > > https://reviews.apache.org/r/64384/ and share the feedback about any > > issues > > it causes (or doesn't cause). > > > > Best regards, > > -- > > Benno Evers > > Software Engineer, Mesosphere > > > -- Cheers, Zhitao Li

Container launch metrics on agent

comparative baseline of the above metric? If not, should we add one? 2) does the `errors` metric above also cover nested and standalone containers? Thanks! -- Cheers, Zhitao Li

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

ild > system to CMake and to port Mesos onto Windows. > > Here is his committer candidate checklist for your perusal: > https://docs.google.com/document/d/1MfJRYbxxoX2-A- > g8NEeryUdUi7FvIoNcdUbDbGguH1c/ > > Congrats Andy! > ~Joseph > -- Cheers, Zhitao Li

Re: Design doc: Relaxing Agent State Recovery on Restart

board and created a second revision of the design > doc. > > As before, all comments are highly welcomed: > > > https://docs.google.com/document/d/1hu0Ufi6gdskNEd7kY1sDx8ST67PAh > 9rJELRTXJzJGX0/edit?usp=sharing > > Best regards, > Benno > > On Sun, Nov 5, 20

Re: Design doc: Relaxing Agent State Recovery on Restart

comments and suggestions are welcome and highly valued. > > Best regards, > -- > Benno Evers > Software Engineer, Mesosphere > -- Cheers, Zhitao Li

Re: Updating running tasks in-place

a/browse/MESOS-1279> > (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: CMake build refactoring

> >>> target_link_libraries(mesos-agent PRIVATE mesos) > >>> > >>> All necessary link and compilation flags are parsed by CMake through > the > >>> dependency graph as it visits libmesos as the mesos-agent dependency. > >>> > >>> I keep an updated tree on GitHub here for easy testing: > >>> https://github.com/andschwa/mesos/blob/cmake-refactor/src/sl > >>> ave/CMakeLists.txt > >>> > >>> As we move closer to deprecating Autotools, I wanted to ensure that the > >>> replacement build system was as correct and easy-to-use as possible. As > >>> with any build system (and any software engineering effort), there is > >>> always more to clean up and improve. However, I am satisfied with the > >>> result of my efforts, and I hope this build system makes your work as > >>> developers easier. If you have the time, please take a look at the the > >>> patches and give it a test. Let me know know I can make it work better > >>> for > >>> you. > >>> > >>> Thank you, > >>> > >>> Andrew Schwartzmeyer > >>> > >>> > -- Cheers, Zhitao Li

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

, 2017 11:59:59 PM PDT, and 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: [Proposal] Use jemalloc as default memory allocator for Mesos

nder https://issues.apache.org/jira/browse/MESOS-7876 > > > > It turns out that we could probably even expect a small speedup (1% - 5%) > > as a nice side-effect of this change. > > > > Users who compile Mesos themselves would of course have the option > > to disable jemalloc at configuration time or replace it with their > > memory allocator of choice. > > > > > > > > I'm looking forward to hear any thoughts and comments. > > > > > > Thanks, > > -- > > Benno Evers > > Software Engineer, Mesosphere > > -- Cheers, Zhitao Li

Re: POST vs PUT in v0 HTTP endpoints

to make it consistent. Let me know if there's > any feedback on this! > > Ben > -- Cheers, Zhitao Li

Re: [Proposal] Multiple Containers in Single Mesos Task

level of concept is not worth it. On Sun, Jun 18, 2017 at 10:18 PM, tommy xiao <xia...@gmail.com> wrote: > it looks like Pod. how about upgrade TASK to POD concept? > > 2017-06-16 23:57 GMT+08:00 Zhitao Li <zhitaoli...@gmail.com>: > > > Hi Ben, > >

Inconsistent hook interface for DockerContainerzer and Mesos containerizer

ce to make it invoked in Mesos containerizer. Is there already a plan to create consistent hook regardless of the containerizer being used? If not, should I create a JIRA ticket? Thanks. -- Cheers, Zhitao Li

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

s a major new feature that involved quite 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: [Proposal] Multiple Containers in Single Mesos Task

ame Task. >> >> Please feel free to write your comments and suggestions on the proposal >> draft: >> https://docs.google.com/document/d/1Os5tXUJfJ8Op_YBZR7L8hSHq >> IeO1f9LY2yzKxsOdrwg >> >> Thanks, >> Charles Raimbert & Zhitao Li >> > > -- Cheers, Zhitao Li

Re: Easing the Pain of Code Formatting in Mesos

a gap is enough to stir discussions and render the tool useless > > for > > > some people. > > > > > > I think we should close this gap by adopting ClangFormat as our > > formatting > > > guideline. > > > > > > I don't have a fully fleshed out plan just yet. I'd like to push for > this > > > effort again, > > > as I find it to be very important. > > > > > > I'm just seeking for +1s if you'd like to see a fleshed out plan for > > this. > > > > > > Thanks, > > > > > > MPark > > > > > -- Cheers, Zhitao Li

Re: Isolating metrics collection from master/agent slowness

.mail-archive.com/dev@mesos.apache.org/msg37113.html > > IMHO we should defer looking into the 5th option of sampling/caching > internally until we've thoroughly attempted to avoid tripping through the > Process queue, because if we succeed it will become unnecessary. > > On

Re: GPU Users -- Deprecation of GPU_RESOURCES capability

nt me of implementing this in our org even if it's already available. > > For the addition of the filter, note that this flag would be a temporary > measure that would be removed when the deprecation cycle of the capability > is complete. It would be good to independently consider

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

lot of folks in the community regarding >> > their >> > > patches, questions and etc. He also played 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: Isolating metrics collection from master/agent slowness

Thanks for the feedback, James. Replying to your points inline: On Mon, May 22, 2017 at 10:56 AM, James Peach <jor...@gmail.com> wrote: > > > On May 19, 2017, at 11:35 AM, Zhitao Li <zhitaoli...@gmail.com> wrote: > > > > Hi, > > > > I'd like

Re: GPU Users -- Deprecation of GPU_RESOURCES capability

r > adding this flag if people are currently relying on the GPU_RESOURCES > capability and would like to see it persist > > We welcome any feedback you have. > > Kevin + Ben > -- Cheers, Zhitao Li

Isolating metrics collection from master/agent slowness

; - serving metrics collection from a different libprocess routine. Any thoughts on these? -- Cheers, Zhitao Li

Re: Choice between LOG(FATAL) and EXIT(EXIT_FAILURE)

erred to use EXIT(EXIT_FAILURE). While that was the original > intention, not sure if we have been following that distinction diligently. > > Separately, we should fix EXIT to log at ERROR level instead of just > printing to to stderr. > > On Tue, Aug 30, 2016 at 10:42 AM, Zhitao Li

Re: Version numbers during development

+1 Sent from my iPhone > On May 5, 2017, at 12:56 PM, Neil Conway wrote: > > Our current practice is that when we create a branch for version X, we > bump the version number in the "master" branch to X+1. For example, we > just created the 1.3.x branch, and bumped the

Preventing more than one framework to register as a particular role

Hi, Is it possible to configure Mesos (maybe ACL part?) to ensure that certain roles can have at most one framework (regardless of active or not) to register? -- Cheers, Zhitao Li

3 way merge support in apply-reviews.py committed

o Michael Park to shepherd and committed the patch <https://reviews.apache.org/r/55732/>. Enjoy! -- Cheers, Zhitao Li

Difference between registered() and reregistered() in scheduler driver

in such a case. Can someone provide some insights on what condition would trigger each call? Thanks. -- Cheers, Zhitao Li

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

conds. > >>> > >>> Our client has a Mesos framework that runs 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

Proposal for evaluating Mesos scalability and robustness through stress test.

e 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: Metrics collection affected when libprocess queue builds up

uivalent to suggestion (3), as it was > designed for Java-style programs with locking as opposed to actors: > > http://metrics.dropwizard.io/3.1.0/getting-started/#gauges > > On Fri, Dec 30, 2016 at 10:34 AM, Zhitao Li <zhitaoli...@gmail.com> wrote: > > > Hi Benjami

Re: Optimize libprocess performance

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 <sut...@huawei.com> > > > > > > > > > > > -- Cheers, Zhitao Li

Re: Metrics collection affected when libprocess queue builds up

tem, making debugging/fighting the problem very hard. > > > > On Mon, Dec 19, 2016 at 9:23 PM, haosdent <haosd...@gmail.com> wrote: > > > > > Hi, @zhitao > > > > > > > the `/metrics/snapshot` could take 10-30 seconds to respond. > > >

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

s, 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 Detection > Solr &

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 <jor...@gmail.com> wrote: > > > > > > > On Dec 19, 2016, at 9:43 AM, Zhitao Li <zhitaoli...@gmail.co

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

e header. I don't know > if this is enough for your use case though. > > — > *Joris Van Remoortere* > Mesosphere > > On Mon, Dec 19, 2016 at 9:58 AM, James Peach <jor...@gmail.com> wrote: > > > > > > On Dec 19, 2016, at 9:43 AM, Zhitao Li <zhitaoli...@gmail.com>

Structured logging for Mesos (or c++ glog)

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

Metrics collection affected when libprocess queue builds up

to track metrics independently from libprocess's queue? -- Cheers, Zhitao Li

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

cklist > <https://docs.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

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

ase is available at: > > > https://git-wip-us.apache.org/repos/asf?p=mesos.git;a=blob_ > > plain;f=CHANGELOG;hb=1.1.0-rc3 > > > > > > > > > > > The candidate for Mesos 1.1.0 release is available at: > > > https://dist.apache.org/repos/dist/dev/mesos/1.1.0-rc3/ > > mesos-1.1.0.tar.gz > > > > > > The tag to be voted on is 1.1.0-rc3: > > > https://git-wip-us.apache.org/repos/asf?p=mesos.git;a= > commit;h=1.1.0-rc3 > > > > > > The MD5 checksum of the tarball can be found at: > > > https://dist.apache.org/repos/dist/dev/mesos/1.1.0-rc3/ > > 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-rc3/ > > 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-1166 > > > > > > Please vote on releasing this package as Apache Mesos 1.1.0! > > > > > > The vote is open until Wednesday Nov 9 14:00:29 CET 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: On increasing visibility into experimental features.

lease, without searching the CHANGELOG for when and > whether a certain feature became production-ready. > > What do you think? > > AlexR. > -- 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: Non-checkpointing frameworks

s that checkpointing requires >>> >> some additional disk I/O at the agent. >>> >> >>> >> 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: Welcome Qian Zhang as a new committer!

ck. He is currently working on OCI > <https://github.com/opencontainers/image-spec> support in Mesos, trying to > enable Mesos to launch OCI containers. > > More details can be found in his committer candidate checklist > <https://docs.google.com/document/d/1p5MyCoWhZC2sAsQwsbSQUaCiAi1- > 7mjWXei9D9SaYUU/edit?usp=sharing> > . > > Qian, thank you for your great work to the project so far. Would love to > see more! > > - Jie > -- Cheers, Zhitao Li

Re: How many roles are we supported?

o try it :). It's better for us >>> (Mesos Dev) to provide suggestion :). >>> >>> On Wed, Sep 7, 2016 at 11:27 AM Zhitao Li <zhitaoli...@gmail.com> wrote: >>> >>>> I think polling user group for how people uses or plan to use Mesos will &

Re: Adding "syntax=proto2" to Mesos public protobuf files

eak anything, since by omitting the syntax > > specification we're effectively setting it to the default, "proto2". As a > > quick test, I added `syntax = "proto2";` to the top of mesos.proto, built > > Mesos, and then ran some tests - it seems to work fine! > >

Re: How many roles are we supported?

> Da (Klaus), Ma (马达), PMP® | Software Architect > IBM Platform Development & Support, STG, IBM GCG > +86-10-8245 4084 | mad...@cn.ibm.com | http://k82.me > -- Cheers, Zhitao Li

Adding "syntax=proto2" to Mesos public protobuf files

for protoc to work correctly. It'll be better if this can be added upstream. This is not really urgent or blocker, just something nice to have. Thanks! -- Cheers, Zhitao Li

Choice between LOG(FATAL) and EXIT(EXIT_FAILURE)

see we have about 100 call sites to LOG(FATAL) and 200 call sites to EXIT(EXIT_FAILURE) at the moment. Many thanks! -- Cheers, Zhitao Li

Re: Integer version macro in header for conditional compilation

= 1 .. #endif #endif ``` The above samples shows if you are using code which only compiles after Mesos 1.0. Please let me know if you have more questions. Cheers, Zhitao Li On Thu, Aug 11, 2016 at 12:25 PM, Vinod Kone <vinodk...@apache.org> wrote: > +kapil,till,adam > > On Thu,

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

;> >> >>> >> 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

Integer version macro in header for conditional compilation

in mesos codebase itself. Can anyone who has a module which already refers these macros let us know whether this can break existing builds? Thanks! -- Cheers, Zhitao Li

Looking for shepherd for MESOS-4638

Our modules requires conditional compile because we need to make sure we can cross version boundary during upgrade cycles, so I'm interested in getting this fixed. Can some committer help to shepherd? (Joris, from git blame it seems you added these macros :) Thanks. -- Cheers, Zhitao Li

Re: Notification: Community Meeting @ Thu Aug 11, 2016 3pm - 4pm (Apache Mesos)

Can we include timezone, or are these always local to what I receive? On Wed, Aug 10, 2016 at 5:03 PM, Michael Park <mp...@apache.org> wrote: > > -- Cheers, Zhitao Li

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

is far more easy to > setup/use. > > Olivier > > > > I would appreciate it if you 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: [VOTE] Release Apache Mesos 1.0.0 (rc4)

pport 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: Metrics for custom modules

, you can add your > metrics via `process::metrics::add(...)`. Those will be exposed via the > same old `/metrics/snapshot` endpoint. > > On Wed, Jul 13, 2016 at 5:39 PM, Zhitao Li <zhitaoli...@gmail.com> wrote: > > > Hi, > > > > I'm not sure whether this

Metrics for custom modules

, Zhitao Li

  1   2   >