On Mon, Apr 25, 2016 at 8:40 AM, Thomas Petr <tp...@hubspot.com> wrote:
> The only thing that ended up fixing the situation was bouncing our > scheduler (~10 minutes after the restarted slaves joined the cluster) -- > the act of failing over the framework appeared to "recover" the missing > resources: > What do the master logs say when the slave is registered with a new id?
