[AURORA-652] GC Executor termination should be co-ordinated by the scheduler

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Fix Version/s: 0.8.0
• Component/s: Reliability
• Assignee: Unassigned
• Reporter: Vinod Kone
• Created: 13/Aug/14 19:29
• Updated: 04/May/15 14:28
• Resolved: 08/Sep/14 19:22

Description

Currently there is no co-ordination between when the gc executor exits and when a gc task is launched. This results in a race where a slave might launch a task on that just exited (but the slave doesn't know about it yet) executor.

This problem is exacerbated during aurora failover because a slew of gc tasks are launched increasing the probability of the race across the cluster.
While Aurora-608 will reduce the probability, coordinating the gc executor exit via aurora seems like the right solution.

Issue Links

• relates to: AURORA-608 GcExecutorLauncher should throttle initial activity spike