Hey folks,

Is there a best practice for rolling out FrameworkInfo changes? We need to
set checkpoint to true, so I redeployed our framework with the new settings
(with tasks still running), but when I hit a slave's stats.json endpoint,
it appears that the old FrameworkInfo data is still there (which makes
sense since there's active executors running). I then tried draining the
tasks and completely restarting a Mesos slave, but still no luck.

Is there anything additional / special I need to do here? Is some part of
Mesos caching FrameworkInfo based on the framework ID?

Another wrinkle with our setup is we have a rather large failover_timeout
set for the framework -- maybe that's affecting things too?

Thanks,
Tom

Reply via email to