Hi,
As we are all excited about release 1.0.0, it's never too early to talk
about next big thing: Mesos 2.0.0. What major things should be done next?
I believe there are still many features you desire in Mesos and some of
them are already under development. I'd like to collect your minds and
ce, without
ZK
> > the quorum is hard-coded to 1.
> >
> > For (#2), trying to understand what you mean by replicated log being
> > pluggable? You mean turning of replicated log on the Master for storing
> > Registrar information?
> >
> > On Fri, Jul 8, 2016 at 2:26 AM
Hi,
We are working on a Mesos module to substitute Zookeeper with Etcd.
Contender and detector are done through modulerized interfaces, however,
replicated_log is still coupled with ZK. Here are my questions:
#1 What's the difference between replicated_log with/without ZK? Without
flag --zk,
Hi Greg,
No problem, just wanted to see what's going on in the community.
One way or another, some people somewhere in this world would suffer a bit
and +1 for the idea of rotating. Personally I don't mind staying up late
(which I always do anyway) or get up early once a while.
Cheers,
/J
Greg
o
> > > get
> > > > a sense from other community members as well through this email.
Please
> > > let
> > > > us know what you think.
> > > >
> > > > Note that even if we move to Slack, we will make sure people can
still
> > > &
Hi,
I find marking protobuf field as 'required' sometimes causing trouble:
serializing a message without filling up required field generates errors
and this is hard to change due to backwards compatibility. And this message
type is actually discouraged by protobuf:
+1 Slack!
/J
Vaibhav Khanduja wrote on 06/16/2016 22:26:27:
> From: Vaibhav Khanduja
> To: dev@mesos.apache.org
> Date: 06/16/2016 22:26
> Subject: Re: Notification: Community Meeting @ Thu Jun 16, 2016 3pm
> - 4pm (Apache Mesos)
>
> + 1
Hi,
I'm getting this error when compiling latest code on OSX:
In file included
from ../../src/tests/containerizer/provisioner_backend_tests.cpp:17:
In file included
from ../../3rdparty/libprocess/include/process/gtest.hpp:16:
In file included
from
fter that time point have not added to it.
>
> Refer:
> http://search-hadoop.com/m/0Vlr6NhCPaWHRX31=Re+Where+s+Meses
> +design+documents
>
> >Also, flat folder structure is a bit tricky
>
> Do you have any suggestions? I could update them according to your ideas
ll design docs
>
> It's here
> https://cwiki.apache.org/confluence/display/MESOS/Design+docs+--+Shared
+Links
>
> On Thu, May 26, 2016 at 2:16 PM, Jay JN Guo <guojian...@cn.ibm.com>
wrote:
>
> >
> > Hi folk,
> >
> > Do we have a place (e.g. google driver
Hi folk,
Do we have a place (e.g. google driver directory) to aggregate all design
docs? I think it makes life easier for people to navigate and dig up
history.
cheers,
/J
Great! count me in pls. As well as xingz...@cn.ibm.com
cheers,
/J
"Yongqiao Wang" wrote on 05/21/2016 21:16:46:
> From: "Yongqiao Wang"
> To: "dev"
> Date: 05/21/2016 21:18
> Subject: Re: RE: [REVIEW PROCESS] Proposal for
- net::links() -> stout/net.hpp
- Personally, I'm not very familiar with CLion build. Maybe somebody else
could answer that.
- I think this is very much related to dev mailing list, so +dev
/J
Frank Scholten wrote on 05/17/2016 20:47:12:
> From: Frank Scholten
Hi,
The script was run and submitted here: https://reviews.apache.org/r/46075/
It was not committed along with the patch though. I've sent a notice to
@Jie.
Since the change is included in the patch as @haosdent mentioned, I guess
we could drop the one I created.
Thanks for reminding!
Cheers,
+1
Although we really need to agree on one single style and stick to it.
I thought all mails sending to dev@mesos.apache.org would be [MESOS-dev] by
default.
So I don't know how much sense it would make to have this first label. Even
though I strongly
agree with @guangya on hierarchical labels.
15 matches
Mail list logo