+1
On Tue, Jun 12, 2018 at 11:16 AM, Renan DelValle wrote:
> Kicking the vote off with a +1 from me since I feel it will simplify our
> patch submission process and lower the difficulty bar for new contributors.
>
> On Tue, Jun 12, 2018 at 11:14 AM Renan DelValle wrote:
>
>> All,
>>
>> I
+1, downloaded and ran tests for each OS
On Thu, May 3, 2018 at 12:20 PM, Stephan Erb wrote:
> +1 for the release as is
>
> Am 3. Mai 2018 21:05:32 MESZ schrieb Renan DelValle :
>>All,
>>
>>Do we want to keep the vote open or should I close it as failed?
All,
I propose that after we centralize SLA logic within the scheduler, we
move to implement SLA-Aware updates as well. Linked is a short
document with the proposed UX.
https://docs.google.com/document/d/1lCoDyoX26qrGrptrgO7vJHqYR_L2CBRGFIywsAd8uQo/edit?usp=sharing
I appreciate any comments and
hread.html/1b8fd10e151054a85c9ea3dc808f7fecb9a87fe5f5e87b10caa46e2a@%3Cdev.mesos.apache.org%3E
Cheers,
Jordan Ly
t;> > the leading scheduler that consumes stable data (that is not affected by
>> > minor inconsistencies).
>> >
>> > On Wed, Jul 26, 2017 at 10:31 AM, David McLaughlin <
>> dmclaugh...@apache.org
>> > >
>> > wrote:
>> >
>> >
Hello everyone!
I've created a document with an initial proposal to reduce leader
failover time by eagerly reading and replaying the replicated log in
followers:
https://docs.google.com/document/d/10SYOq0ehLMFKQ9rX2TGC_xpM--GBnstzMFP-tXGQaVI/edit?usp=sharing
We wanted to open up this topic for