[
https://issues.apache.org/jira/browse/AURORA-608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14076964#comment-14076964
]
Maxim Khutornenko commented on AURORA-608:
------------------------------------------
https://issues.apache.org/jira/browse/MESOS-1646
> 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)
