aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Farner (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AURORA-608) GcExecutorLauncher should throttle initial activity spike
Date Mon, 28 Jul 2014 20:25:39 GMT

    [ https://issues.apache.org/jira/browse/AURORA-608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14076763#comment-14076763
] 

Bill Farner commented on AURORA-608:
------------------------------------

{quote}
This proved to be a perf problem for Mesos master under certain conditions.
{quote}

Should this rather be considered a bug in mesos?  Seems reasonable that the master should
not extend offers it does not want accepted.

> GcExecutorLauncher should throttle initial activity spike
> ---------------------------------------------------------
>
>                 Key: AURORA-608
>                 URL: https://issues.apache.org/jira/browse/AURORA-608
>             Project: Aurora
>          Issue Type: Task
>          Components: Scheduler
>            Reporter: Maxim Khutornenko
>            Assignee: Maxim Khutornenko
>
> The current implementation of the GcExecutorLauncher randomizes the GC activity by spreading
different host GC execution over the hour. It does not, however, protect from the startup
spike of accepted GC offers before the host cache is populated. This proved to be a perf problem
for Mesos master under certain conditions.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message