Description
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.
Attachments
Issue Links
- is related to
-
AURORA-652 GC Executor termination should be co-ordinated by the scheduler
-
- Resolved
-
- relates to
-
-
- Open
-