On Mon, Dec 11, 2017 at 9:53 AM, James Peach wrote:
>
> > On Dec 11, 2017, at 8:55 AM, Zhitao Li wrote:
> >
> > Hi,
> >
> > We are running tasks which has very large docker images and tasks which
> use
> > much smaller images in our clusters, Therefore,
1) My guess is that we only added the errors because we alerted on there
being an error increase. I assume you also care about every error? Having a
'success' count and 'total' count sounds reasonable to me.
2) Not sure, have you read the code? What would you want to be the case?
Would you need
This is huge guys. I just re-tweeted it from the `ApacheMesos` twitter
account as well.
Thanks Dmitry, Michael, Yan and Ben for driving these changes.
On Mon, Dec 11, 2017 at 1:16 PM, Benjamin Mahler wrote:
> I was going to send this out to the dev@ list but I'll reply here
I was going to send this out to the dev@ list but I'll reply here instead :)
This is a report on the progress we've made recently in the performance
working group, specifically highlighting the improvements to master
failover performance. Special thanks to Dmitry Zhuk, Michael Park and Yan
Xu for
This is AWESOME!
- Jie
On Mon, Dec 11, 2017 at 11:54 AM, wrote:
> Repository: mesos
> Updated Branches:
> refs/heads/master 83f81b7b2 -> e7244ae1e
>
>
> Added a performance working group December 2017 blog post.
>
> This blog post discusses the master failover performance
> On Dec 11, 2017, at 8:55 AM, Zhitao Li wrote:
>
> Hi,
>
> We are running tasks which has very large docker images and tasks which use
> much smaller images in our clusters, Therefore, we expect to see occasional
> violation of --executor_registration_timeout for tasks
Hi,
We are running tasks which has very large docker images and tasks which use
much smaller images in our clusters, Therefore, we expect to see occasional
violation of --executor_registration_timeout for tasks which has uncached
large docker images.
I wonder whether we can introduce some