The doc mentioned that the scheduler will start an update subject to the heartbeat countdown, and if it doesn't receive a heartbeat it will pause the update. Why not start with the update paused-due-to-no-heartbeat to fail-fast any connectivity issues between the service providing the heartbeats and the scheduler?
On Fri, Oct 10, 2014 at 12:47 PM, Maxim Khutornenko <ma...@apache.org> wrote: > Hi all, > > We are proposing a new feature for the scheduler updater, which you > may find helpful. > > I have posed a brief feature summary here: > > https://github.com/maxim111333/incubator-aurora/blob/hb_doc/docs/update-heartbeat.md > > Please, reply with your feedback/concerns/comments. > > Thanks, > Maxim >
