----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/37180/#review97064 -----------------------------------------------------------
src/master/master.cpp (line 4904) <https://reviews.apache.org/r/37180/#comment152785> If the allocator calls inverse callback followed by an offer callback, will the two messages be handled in two separate threads of the framework? I think it will be framework's responsibility to ensure data synchronization between the two threads? - Jian Qiu On 八月 26, 2015, 2:13 a.m., Joris Van Remoortere wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/37180/ > ----------------------------------------------------------- > > (Updated 八月 26, 2015, 2:13 a.m.) > > > Review request for mesos, Benjamin Hindman, Artem Harutyunyan, and Joseph Wu. > > > Bugs: MESOS-1474 > https://issues.apache.org/jira/browse/MESOS-1474 > > > Repository: mesos > > > Description > ------- > > See summary. > > > Diffs > ----- > > src/master/master.hpp 36c67599ef2c470da8d95f2caf926a154342d2cc > src/master/master.cpp 95207d24db0aa052eb70c4cc7eb75d0611c365cf > > Diff: https://reviews.apache.org/r/37180/diff/ > > > Testing > ------- > > The tests break as expected. > With the scheduler API change there are CHECKs that fail. > Once we update the API these will be resolved. > > > Thanks, > > Joris Van Remoortere > >
