Thanks Ben! I have let Shane know this to hold off on going into the attic,
and happy to help on the Cgroups v2 support :-)
Regards,
Qian Zhang
On Sat, Jan 13, 2024 at 8:48 AM Samuel Marks wrote:
> On latest commit 5109b9069b62510ab6d0cc0c78a9ed8327d3986a `fd -epy | wc -l`
> shows 73
Hi Shane,
Please hold off on moving Mesos into the attic, Ben and his team members
will contribute some substantial code changes to Mesos, thanks Ben and your
team!
Regards,
Qian Zhang
On Tue, Nov 14, 2023 at 3:17 PM Charles-François Natali
wrote:
> Still using Mesos - it's stable, bor
may have
to move Mesos to attic.
Regards,
Qian Zhang
On Tue, Mar 21, 2023 at 2:56 AM Benjamin Mahler wrote:
> Also if you are still a user of mesos, please chime in.
> Qian, it might be worth having a more explicit email asking users to chime
> in as this email was tailored mor
illing to actively
contribute to the project as a contributor, please reply to this email,
thanks!
Regards,
Qian Zhang
Thanks Dave for taking care of this!
I'd prefer to host the MesosCon 2015 videos together with the videos of
other MesosCons so we will have a single place for all videos.
Regards,
Qian Zhang
On Tue, Mar 14, 2023 at 2:20 AM Dave Lester wrote:
> I’m looking into options for moving vi
Thanks Andreas!
Regards,
Qian Zhang
On Tue, Jul 26, 2022 at 7:36 PM Andreas Peters
wrote:
> I fixed the gem error. Just have to update ruby to a newer version. At
> least, is working on my local system. :-)
>
> https://github.com/apache/mesos/pull/444
>
>
> Am 28.0
Hi Andreas,
Could you please create an infra ticket (similar to this one
<https://issues.apache.org/jira/browse/INFRA-22262>) to ask the Apache
infra team for help? Thanks!
Regards,
Qian Zhang
On Tue, Feb 15, 2022 at 3:32 PM Andreas Peters
wrote:
> Hi,
>
> the Mesos-Mini pipel
ust a normal function call inside the
container which packages the supported language runtime and the function or
an on-demand short-live container dedicatedly launched for each request?
Regards,
Qian Zhang
On Wed, Sep 8, 2021 at 9:30 PM John Siegrist wrote:
> Hi Qian,
>
> After looking i
ces offers from
Mesos master. Could you please elaborate a bit more on the specific
requirements for Mesos to support serverless workload?
Regards,
Qian Zhang
On Tue, Sep 7, 2021 at 8:27 PM John Siegrist wrote:
> Hello All,
>
> In going through the mail archive before subscribing
Awesome, thanks Charles and Renán!
Regards,
Qian Zhang
On Sat, Sep 4, 2021 at 4:57 PM Charles-François Natali
wrote:
> Benjamin Bannier has kindly invited me to join the
> https://github.com/orgs/mesos/ organisation, so I now have the
> required permissions - I'll get in touch w
Congratulations Charles! Well deserved!
Regards,
Qian Zhang
On Mon, Aug 16, 2021 at 6:33 AM Charles-François Natali
wrote:
> Thanks!
>
> Cheers,
>
> Charles
>
>
> On Sun, Aug 15, 2021, 21:32 Andreas Peters wrote:
>
> > Congratulations Charles. :-) I'm v
Thanks Martin!
Regards,
Qian Zhang
On Thu, Jul 22, 2021 at 4:01 AM Martin Tzvetanov Grigorov <
mgrigo...@apache.org> wrote:
> Hi,
>
> I've sent the connection details to the new ARM64 VM to Qian Zhang and
> Apache Infra team.
> Please follow https://issues.apache.org/ji
Hi Martin,
Please let me know if you need anything from me.
Regards,
Qian Zhang
On Fri, Jul 16, 2021 at 4:34 PM Martin Tzvetanov Grigorov <
mgrigo...@apache.org> wrote:
> Hi,
>
> Sorry, for the late reply. I was on a vacation.
>
> Tomek, I was about to contact you to sh
/jira/browse/INFRA-15261.
Regards,
Qian Zhang
On Tue, Jun 29, 2021 at 3:26 AM Tomek Janiszewski wrote:
> I created a request to Works On ARM
> https://github.com/WorksOnArm/cluster/issues/278
> If you are interested about history of Mesos on ARM
> https://twitter.com/search?q=ARM%
Considering we are short-handed now, I think we should decide to close old
Jira tickets or triage and work on the new ones. I'd prefer the latter. Or
we should just work on the high priority tickets (e.g. blocker and
critical) regardless of their age.
Regards,
Qian Zhang
On Tue, Jun 1, 2021
ou'd like to contribute to :)
Regards,
Qian Zhang
On Mon, May 31, 2021 at 3:08 AM Charles-François Natali
wrote:
> Le dim. 30 mai 2021 à 16:09, Qian Zhang a écrit :
> > [...] So given the
> > active committers and contributors that we have in the community, I do
> not
>
and select some high priority ones to work on.
3. Add at least one new committer.
Please let me know for any comments / suggestions, thanks!
Regards,
Qian Zhang
On Sun, May 30, 2021 at 7:59 PM Zahoor wrote:
> Hi
>
> Better to rewrite/redesign Mesos with a more popular language (like
sos unusable on a recent Linux
distro
Can you please elaborate a bit on this? Do you mean Mesos not working on a
recent Linux distro? If so, I think we can start to fix the issues and
maybe do a patch release for that.
Regards,
Qian Zhang
On Fri, May 21, 2021 at 2:57 AM Charles-François Nat
for it, maybe HPC
is a good direction? But we definitely need more concrete ideas for it.
Please feel free to add any comments/suggestions, thanks!
Regards,
Qian Zhang
Hi Andreas
Do you mean marking issues in https://issues.apache.org/jira/ as resolved?
I do not think you need special permission to do that.
Regards,
Qian Zhang
On Thu, May 20, 2021 at 3:18 PM Andreas Peters
wrote:
> Hey,
>
>
> what I have to do, to get the permissions to
Hi Marc,
I will take the lead on this project. My plan is to collect the
requirements from the community and then come up with a roadmap plan which
I will send here to discuss.
Please feel free to let me know for any comments / suggestions, thanks!
Regards,
Qian Zhang
On Fri, Apr 30, 2021
Thanks Vinod! Really appreciate your contributions and guidance to this
great project.
It's a huge honor to be the new PMC chair, I will try my best to work with
the community and make Mesos better.
Regards,
Qian Zhang
On Fri, Apr 30, 2021 at 1:16 AM Thomas Langé wrote:
> That's really g
Hi folks,
Please reply to this mail if you plan to actively contribute to Mesos and
want to become a new Mesos committer, thanks!
Regards,
Qian Zhang
Hi folks,
Please reply to this mail if you plan to actively contribute to Mesos and
want to become a committer and PMC member in future.
Regards,
Qian Zhang
Hi Folks,
To reboot this awesome project, I'd like to collect feature requests for
Mesos. Please let us know your requirements for Mesos and whether you or
your organization would like to contribute to the implementation of the
requirements. Thanks!
Regards,
Qian Zhang
to
set up a roadmap for the project to move forward.
Regards,
Qian Zhang
On Thu, Feb 18, 2021 at 9:16 PM Andrei Sekretenko
wrote:
> IIUC, Attic is not intended for projects which still have active users
> and thus might be in need of fixing bugs.
>
> Key items about moving proj
+1
Regards,
Qian Zhang
On Thu, Nov 19, 2020 at 4:16 AM Till Toenshoff wrote:
> +1
>
> Build using Apple clang version 12.0.0 (clang-1200.0.32.27) and ran on
> macOS 11.0.1 (20B29).
>
> > On 17. Nov 2020, at 15:53, Andrei Sekretenko
> wrote:
> >
> > Hi a
+1 (binding)
Regards,
Qian Zhang
On Thu, May 28, 2020 at 12:56 AM Benjamin Mahler wrote:
> +1 (binding)
>
> On Mon, May 18, 2020 at 4:36 PM Andrei Sekretenko
> wrote:
>
>> Hi all,
>>
>> Please vote on releasing the following candidate as Apache Me
Hi all,
The vote for Mesos 1.9.0 (rc3) has passed with the
following votes.
+1 (Binding)
--
Vinod Kone
Gilbert Song
Chun-Hung Hsiao
There were no 0 or -1 votes.
Please find the release at:
https://dist.apache.org/repos/dist/release/mesos/1.9.0
It is recommended to
Hi all,
Please vote on releasing the following candidate as Apache Mesos 1.9.0.
1.9.0 includes the following:
* Agent draining
* Support configurable /dev/shm and IPC namespace.
* Containerizer debug endpoint.
*
Hi all,
Please vote on releasing the following candidate as Apache Mesos 1.9.0.
1.9.0 includes the following:
* Agent draining
* Support configurable /dev/shm and IPC namespace.
* Containerizer debug endpoint.
*
6138>
have been reverted on 1.9.x branch, so I will cut rc2 later today.
Regards,
Qian Zhang
On Wed, Aug 28, 2019 at 4:40 AM Vinod Kone wrote:
> I see. That's reduces the risk considerably than what I originally thought
> but I guess still risky to introduce it so late?
>
> O
Hi all,
Please vote on releasing the following candidate as Apache Mesos 1.9.0.
1.9.0 includes the following:
* Agent draining
* Support configurable /dev/shm and IPC namespace.
* Containerizer debug endpoint.
*
for this new release, please set
"Target Version" as "1.9.0" and mark it as "Blocker" priority.
Regards,
Qian Zhang
Please feel free to let me know if you have any comments/feedbacks, you can
reply this mail or comment on the design doc directly.
Thanks!
Regards,
Qian Zhang
<https://docs.google.com/document/d/1AU5IXMbR0AGlustNs-_62L4M3UvOuYKgjun8SlnCsS0/edit?usp=sharing>.
Please feel free to let us know if you have any comments/feedbacks, you can
reply this mail or comment on the design doc directly. Thanks!
Regards,
Qian Zhang
Agree with Gilbert, we should actually run nested container (rather than
just debug container) as the same user of its parent container by default.
Please let me know if you have any concerns, thanks!
Regards,
Qian Zhang
On Sat, Nov 3, 2018 at 2:56 AM Gilbert Song wrote:
> @James Pe
Congrats Meng!
Regards,
Qian Zhang
On Wed, Oct 31, 2018 at 4:50 PM Vinod Kone wrote:
> Congrats Meng!
>
> Thanks,
> Vinod
>
> On Oct 31, 2018, at 4:26 PM, Gilbert Song wrote:
>
> Well deserved, Meng!
>
> On Wed, Oct 31, 2018 at 2:36 PM Benjamin Mahler
expects.
So I created MESOS-9332 <https://issues.apache.org/jira/browse/MESOS-9332> and
propose to run debug container as the same user of its parent container
(i.e., the task to be debugged) by default. Please let me know if you have
any comments, thanks!
Regards,
Qian Zhang
esos/blob/1.7.0/src/docker/docker.cpp#L152> for
details). I think it does not make sense for us to support Docker 1.0.0
which is too old, so I propose to update the minimal supported Docker
version in Mesos to 1.8.0.
Please let me know for any comments, thanks!
Regards,
Qian Zhang
Does this imply that when it updates the ACEs for the container GID, it
also needs to update the default ACLs on all directories?
Currently I do not think we need to set the default ACL on the volume root
dir.
Regards,
Qian Zhang
On Fri, Aug 17, 2018 at 12:38 AM, James Peach wrote:
>
>
>
Hi Folks,
We found some issues for the solutions of this project and propose a better
one, see here
<https://docs.google.com/document/d/1QyeDDX4Zr9E-0jKMoPTzsGE-v4KWwjmnCR0l8V4Tq2U/edit#heading=h.tjuy5xk67tuu>
for details. Please let me know if you have any comments, thanks!
Regards,
Qian
/edit?usp=sharing>
.
Please feel free to let us know for any comments, thanks!
Regards,
Qian Zhang
se feel free to comment on the doc. Thanks!
Regards,
Qian Zhang
t says nothing about
which credentials can write to it.
Can you please elaborate a bit on this? What would you suggest for the "rw`
volume mode?
Regards,
Qian Zhang
On Fri, Apr 27, 2018 at 12:07 PM, James Peach <jor...@gmail.com> wrote:
>
>
> > On Apr 26, 2018, at 7:25 PM, Qian Zh
me due to the ownership issue
though the volume's mode is set to "rw". So in this case, how should
framework handle it? And if we want to document it, what is our recommended
solution in the doc?
Regards,
Qian Zhang
On Fri, Apr 27, 2018 at 1:16 AM, James Peach <jpe...@apache.org>
Hi Aditya,
Yeah, you are right. `hostSecretPath` is a sub-directory under agent's
runtime dir, and the default value of agent's runtime dir is `/var/run/mesos`
which is a tmpfs. So the secret is written to tmpfs on agent host.
Regards,
Qian Zhang
On Sat, Apr 21, 2018 at 8:19 AM, Aditya Bhave
the container is launched.
Regards,
Qian Zhang
On Fri, Apr 20, 2018 at 2:47 PM, Gilbert Song <gilb...@apache.org> wrote:
> IIUC, your assumptions are all correct.
>
> @Kapil, could you please confirm? Maybe we could improve the document at
> the next Docathon.
>
> Gilbert
>
>
Hi Marc,
I have shared the design doc to ensure anyone (no sign-in required) with
the link can comment, can you try again?
Regards,
Qian Zhang
On Tue, Apr 10, 2018 at 1:04 PM, Marc Roos <m.r...@f1-outsourcing.eu> wrote:
>
> Cannot access it
>
>
>
> -Original M
Please feel free to let me know if you have any comments/feedbacks, you can
reply this mail or comment on the design doc directly. Thanks!
Regards,
Qian Zhang
Congrats Zhitao!
Regards,
Qian Zhang
On Tue, Mar 13, 2018 at 6:30 AM, Jason Lai <ja...@jasonlai.net> wrote:
> Huge congrats, Zhitao!
>
> It is super awesome to have you represent Uber for our Mesos open source
> efforts! Well deserved!
>
> Jason
>
> On Mon, Mar
For the new UPDATE_QUOTA call, do we allow setting limit lower than role's
existing allocation? If yes, does operator have to do it with the 'force'
flag?
Regards,
Qian Zhang
On Sat, Mar 10, 2018 at 10:40 AM, Benjamin Mahler <bmah...@apache.org>
wrote:
> As discussed during the AP
Congratulations Chun!
Regards,
Qian Zhang
On Sun, Mar 11, 2018 at 2:08 PM, Sam <usultra...@gmail.com> wrote:
> Congrats Chun
>
>
> Regards,
> Sam Chen | APJ Country Director | DC/OS Evangelist
>
> [image: Watch the Video]
> <http://smart
>
Are we going to define min amount for each known resource type (including
disk and gpu)?
Regards,
Qian Zhang
On Wed, Mar 7, 2018 at 6:10 AM, Jie Yu <yujie@gmail.com> wrote:
> Chatted with BenM offline on this. There's another option what both of us
> agreed that it's probably be
Congratulations!
Regards,
Qian Zhang
On Tue, Nov 28, 2017 at 7:10 AM, Jie Yu <yujie@gmail.com> wrote:
> Congrats, Andy!
>
> - Jie
>
> On Mon, Nov 27, 2017 at 3:00 PM, Joseph Wu <jos...@mesosphere.io> wrote:
>
> > Hi devs & users,
> >
> >
And I will backport MESOS-8051 to 1.2.x, 1.3.x and 1.4.x.
Regards,
Qian Zhang
On Fri, Nov 3, 2017 at 9:01 AM, Qian Zhang <zhq527...@gmail.com> wrote:
> We want to backport https://reviews.apache.org/r/62518/ to 1.2.x, 1.3.x
> and 1.4.x, James will work on it.
>
>
>
We want to backport https://reviews.apache.org/r/62518/ to 1.2.x, 1.3.x and
1.4.x, James will work on it.
Regards,
Qian Zhang
On Fri, Nov 3, 2017 at 12:11 AM, Kapil Arya <ka...@mesosphere.io> wrote:
> Please reply to this email if you have pending patches to be backported to
>
Thanks Vinod and James!
So I think the task state transition TASK_KILLING -> TASK_FINISHED is a
bug, we should change it to TASK_KILLING -> TASK_KILLED.
Regards,
Qian Zhang
On Fri, Sep 22, 2017 at 3:27 PM, James Peach <jor...@gmail.com> wrote:
>
> > On Sep 21, 2017, at
it is killed or
terminated on its own), then I think it is OK to receive a TASK_KILLING
followed by a TASK_FINISHED.
Please let us know your thoughts on this issue, thanks!
Regards,
Qian Zhang
Ubuntu seems a relatively big image, have we considered a more lightweight
one, e.g., alpine?
Regards,
Qian Zhang
On Tue, Jun 27, 2017 at 9:38 PM, Jörg Schad <jo...@mesosphere.io> wrote:
> Dear community,
> the current Mesos Docker image (provided by Mesosphere here:
> https://h
os": {
"image": {
"type": "DOCKER",
"docker": {
"name": "busybox"
}
}
},
"network_infos": [
{
"name": "net1"
}
]
}
}
2. In addition to
Congrats Greg!
Regards,
Qian Zhang
On Wed, Jun 14, 2017 at 7:24 AM, Guang Ya Liu <gyliu...@gmail.com> wrote:
> Congrats Greg!!! Very well deserved
>
> On Wed, Jun 14, 2017 at 7:04 AM, Klaus Ma <klaus1982...@gmail.com> wrote:
>
> > Congrats!
> >
>
, is it possible for us to use the new features (like maps) supported
in proto3? And what about the newly introduced .proto file? I think we do
not need to have "syntax = "proto2";" in it, right?
Regards,
Qian Zhang
On Sat, May 27, 2017 at 6:58 AM, Michael Park <mp...@apache.org&
Congratulations Gilbert! Well deserved!!!
Regards,
Qian Zhang
On Thu, May 25, 2017 at 6:54 AM, Klaus Ma <klaus1982...@gmail.com> wrote:
> Congratulations Gilbert!
>
> On Thu, May 25, 2017 at 3:39 AM Greg Mann <g...@mesosphere.io> wrote:
>
>> Congratulations Gil
Congratulations!
Thanks,
Qian Zhang
On Thu, Mar 2, 2017 at 6:43 AM, Greg Mann <g...@mesosphere.io> wrote:
> Woowoo! Congrats Kevin!!
>
> On Wed, Mar 1, 2017 at 2:26 PM, Avinash Sridharan <avin...@mesosphere.io>
> wrote:
>
>> Awesome !! Congrats Kevin !!
>
Congratulations Haosdent! Well deserved! :-)
Thanks,
Qian Zhang
On Sat, Dec 17, 2016 at 8:07 AM, Sam <usultra...@gmail.com> wrote:
> Congratulations Haosdent :)
>
> Sent from my iPhone
>
> > On 17 Dec 2016, at 2:59 AM, Vinod Kone <vinodk...@apache.org> wrote:
> >
> > Haosdent
>
at network is in its
cache but not in the disk, so it can fail framework's request and remove
that CNI network from its cache. So it is kind of lazy delete in cache.
Thanks,
Qian Zhang
On Thu, Dec 8, 2016 at 8:12 AM, Avinash Sridharan <avin...@mesosphere.io>
wrote:
> On Wed, Dec 7, 2016
>
> and requires operators to enable checkpointing on the slaves.
Just curious why operator needs to enable checkpointing on the slaves (I do
not see an agent flag for that), I think checkpointing should be enabled in
framework level rather than slave.
Thanks,
Qian Zhang
On Sun, Oct 16
and comment it,
thanks!
https://docs.google.com/document/d/1Pus7D-inIBoLSIPyu3rl_apxvUhtp3rp0_b0Ttr2Xww/edit?usp=sharing
Thanks,
Qian Zhang
Thanks folks, looking forward to working more with you guys in the
community!
Thanks,
Qian Zhang
On Mon, Oct 10, 2016 at 1:36 AM, Gilbert Song <gilb...@mesosphere.io> wrote:
> Congrats, Qian!
>
> On Sun, Oct 9, 2016 at 10:11 AM, Zhitao Li <zhitaoli...@gmail.com> wrote:
ent but not in master? Is it because
"ContainerInfo.DockerInfo.PortMapping" is DockerContainerizer specific and
we only want to do generic validation in master?
@Jie and @BenM, please also let me know your comments, thanks!
Thanks,
Qian Zhang
Thanks @haosdent's awesome work and @Jie's great shepherding and guidance
on this project!
Thanks,
Qian Zhang
On Wed, Sep 14, 2016 at 7:56 AM, Gilbert Song <gilb...@mesosphere.io> wrote:
> Awesome!
>
> Kudos to @haosdent and @qianzhang!
>
> On Tue, Sep 13, 2016 at 11:2
Hi Olivier,
Can you try TaskInfo.CommandInfo.user?
Thanks,
Qian Zhang
On Thu, Sep 1, 2016 at 4:39 PM, Olivier Sallou <olivier.sal...@irisa.fr>
wrote:
> Hi,
> If Docker image specified a USER in Dockerfile, docker will use this user
> when executing command in container.
>
Yes, the executor will try to connect to agent via 127.0.0.1:5051 in its
own network namespace, but your agent is actually listening on
127.0.0.1:5051 in the host network namespace, so executor can never connect
to agent. You need to have your agent listen on a host interface.
Thanks,
Qian Zhang
to be customized. And I believe Docker
containerizer will be eventually deprecated sometime in future.
Thanks,
Qian Zhang
On Tue, Aug 23, 2016 at 5:42 PM, Olivier Sallou <olivier.sal...@irisa.fr>
wrote:
>
>
> On 08/23/2016 11:36 AM, Yu Wei wrote:
> > Hi,
> >
> >
>
@Vinod, what if the executor talks to Docker engine to create a Docker
container as the task and set the resources of that container more than
task's resources? Will we guard this?
Thanks,
Qian Zhang
On Tue, Jun 28, 2016 at 8:12 AM, Vinod Kone <vinodk...@apache.org> wrote:
> A task do
Congratulations Anand and Joseph! Well deserved!
Thanks,
Qian Zhang
On Fri, Jun 10, 2016 at 5:00 AM, Vinod Kone <vinodk...@apache.org> wrote:
> Hi folks,
>
> I'm happy to announce that the PMC has voted in *Anand Mazumdar *and
> *Joseph
> Wu* as committers and members
I deleted everything in the work dir (/var/lib/mesos/master), and tried
again, the same error still happened :-(
Thanks,
Qian Zhang
On Mon, Jun 6, 2016 at 3:03 AM, Jean Christophe “JC” Martin <
jch.mar...@gmail.com> wrote:
> Qian,
>
> Zookeeper should be able to reach a quorum
I am using the latest Mesos code in git (master branch). However, I also
tried the official 0.28.1 release, but no lock too.
Thanks,
Qian Zhang
On Sun, Jun 5, 2016 at 8:04 AM, Jie Yu <yujie@gmail.com> wrote:
> Which version are you using?
>
> - Jie
>
> On Sat, Jun 4,
--zk=zk://192.168.122.132:2181,
192.168.122.171:2181,192.168.122.225:2181/mesos --quorum=2
--work_dir=/var/lib/mesos/master
And I see the same error for both.
192.168.122.132, 192.168.122.225 and 192.168.122.171 are 3 VMs which are
running on a KVM hypervisor host.
Thanks,
Qian Zhang
On Sun, Jun 5, 2
r 3.4.8 and 3.4.6 with latest code of Mesos, but no
luck for both. Any ideas about what happened? Thanks.
Thanks,
Qian Zhang
Please add me as well, thanks!
Thanks,
Qian Zhang
On Sat, May 21, 2016 at 9:10 AM, Guangya Liu <gyliu...@gmail.com> wrote:
> +1, please count me in as well.
>
> Thanks,
>
> Guangya
>
> On Sat, May 21, 2016 at 2:11 AM, Shivam Pathak <shivam.patha...@gmail.com>
the quickest way to try CNI network support in Mesos from
E2E is: start a Mesos master and a Mesos agent with CNI isolator/some CNI
network configs/some CNI plugins loaded, and run "mesos-executor" to launch
a container to join one CNI network.
Thanks,
Qian Zhang
On Wed, May 18,
Hi Folks,
We are going to delete the master "/observe" HTTP endpoint in the JIRA
ticket MESOS-5408 since this endpoint was introduced a long time ago
for supporting functionality that was never implemented.
Please let us know if you have any comments or concerns, thanks!
Thanks,
Qian Zhang
In that wiki, can we also put the corresponding JIRA ticket link there so
that folks can take a close look at the projects they are interested in?
Thanks,
Qian Zhang
On Fri, Apr 22, 2016 at 8:20 AM, haosdent <haosd...@gmail.com> wrote:
> I would like to know more details about
>
be executed when the previous thread comes in again, right?
Thanks,
Qian Zhang
On Tue, Mar 29, 2016 at 8:50 AM, Jie Yu <yujie@gmail.com> wrote:
> Hi,
>
> While digging a bug reported in, I realized an assumption we shouldn't make
> in our code.
> https://issues.apache.
Done, please review, thanks Neil and Jie.
https://reviews.apache.org/r/44696/
Thanks,
Qian Zhang
On Fri, Mar 11, 2016 at 3:13 AM, Jie Yu <yujie@gmail.com> wrote:
> Good catch.
>
> + Qian, could you please send a patch for that? Thanks!
>
> - Jie
>
> On Thu, Mar
comments in the design doc, thanks!
Thanks,
Qian Zhang
>
> My question is - if the slaves to execute the tasks are decided by the
> scheduler, how does the DRF get used by the master in balancing the slaves?
> Does it not get used for choosing the right slaves for the tasks? Relevant
> pointers to the code are also welcome.
>
I think the DRF
(total: cpus(*):2; mem(*):1024; disk(*):1024;
ports(*):[31000-32000], allocated: cpus(*):2; mem(*):1024; disk(*):1024;
ports(*):[31000-32000]; *cpus(*){REV}:2*)
Thanks,
Qian Zhang
On Thu, Jan 21, 2016 at 5:25 PM, Klaus Ma <klaus1982...@gmail.com> wrote:
> Hi team,
>
> When
Hi Olivier,
Here is the doc of MesosContainerizer:
https://github.com/apache/mesos/blob/master/docs/mesos-containerizer.md
And you may also find the following docs helpful:
https://github.com/apache/mesos/blob/master/docs/containerizer.md
Sure, I have added you as the shepherd, thanks Tim!
2016-01-09 1:44 GMT+08:00 Timothy Chen <tnac...@gmail.com>:
> I'll shepherd this, can you add me to the jira?
>
> Thanks,
>
> Tim
>
> > On Jan 8, 2016, at 7:04 AM, Qian Zhang <zhq527...@gmail.com> wrote:
>
Hi,
Can anyone shepherd https://issues.apache.org/jira/browse/MESOS-4279? I
have posted some findings there, we can do further discussion in the ticket.
Thanks,
Qian Zhang
Hi Folks,
Chris created a JIRA ticket:
https://issues.apache.org/jira/browse/MESOS-4027 for improving task-node
affinity. Basically I think the user story in this ticket is pretty clear:
There are some existing tasks running in some Mesos agents, and a framework
wants to launch a new task, and it
Since we all agree option 2 is the best option for scheduler API's change,
I have updated design doc by marking it as the first option which means it
is the final decision.
I see. However, that operation is not idempotent. Imagine you issue a
> resize request and for some reason, the request
; anyway to figure out whether the framework's request is valid, no?
>
> We can do a online sync soon, if you want to give a pitch on the design.
>
> Cheers,
> Niklas
>
>
> On Thu, Nov 19, 2015 at 6:34 AM, Qian Zhang <zhq527...@gmail.com> wrote:
>
&g
Hi All,
I am currently working on task resizing (MESOS-938), and have drafted a
design doc (see the link below).
https://docs.google.com/document/d/15rVmS2AXLzTDSEugAVDxWuHFUentp82KhL2yzxBCsi8/edit?usp=sharing
Please feel free to review it, any comments are welcome, thanks!
Regards,
Qian
97 matches
Mail list logo
