----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/30978/#review72394 -----------------------------------------------------------
docs/app-framework-development-guide.md <https://reviews.apache.org/r/30978/#comment118461> >persisted durably by the scheduler This is just a suggestion rather than a requirement, right? Persisting status updates may be prohibitively expensive for a scheduler using native Mesos log. Is there a way for the master to fully guarantee reliable delivery of status updates in view of ack timeouts? docs/app-framework-development-guide.md <https://reviews.apache.org/r/30978/#comment118462> No docs for the `acknowledgeStatusUpdate` API? - Maxim Khutornenko On Feb. 13, 2015, 7:38 a.m., Ben Mahler wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/30978/ > ----------------------------------------------------------- > > (Updated Feb. 13, 2015, 7:38 a.m.) > > > Review request for mesos, Niklas Nielsen, Vinod Kone, and Bill Farner. > > > Bugs: MESOS-2347 > https://issues.apache.org/jira/browse/MESOS-2347 > > > Repository: mesos > > > Description > ------- > > This updates the CHANGELOG and upgrades document for the upcoming API change. > > > Diffs > ----- > > CHANGELOG 966661ab5790a5297736121dd7189b4b4131efd6 > docs/app-framework-development-guide.md > e6247b23de3aebbe911a2f72839710c7477008fe > docs/upgrades.md 168e761b7242dc421ff6c7748e2c735de07ab87c > > Diff: https://reviews.apache.org/r/30978/diff/ > > > Testing > ------- > > N/A > > > Thanks, > > Ben Mahler > >
