----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/65072/#review195237 -----------------------------------------------------------
Fix it, then Ship it! src/master/master.cpp Lines 7635 (patched) <https://reviews.apache.org/r/65072/#comment274410> s/do/does/ src/master/master.cpp Lines 7659 (patched) <https://reviews.apache.org/r/65072/#comment274440> Since we've discovered that updating an operation is not necessarily linked to the receipt of an UpdateOperationStatusMessage, I would love if we could refactor this in the future so that we don't have to generate an UpdateOperationStatusMessage in order to update the operation. I created a ticket for this work = https://issues.apache.org/jira/browse/MESOS-8439 Feel free to link it here if you like. - Greg Mann On Jan. 11, 2018, 1:53 p.m., Benjamin Bannier wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/65072/ > ----------------------------------------------------------- > > (Updated Jan. 11, 2018, 1:53 p.m.) > > > Review request for mesos, Gaston Kleiman and Greg Mann. > > > Bugs: MESOS-8422 > https://issues.apache.org/jira/browse/MESOS-8422 > > > Repository: mesos > > > Description > ------- > > An offer operation can be become terminal between any previously > received non-terminal offer operation status update and receiving an > `UpdateSlaveMessage` (e.g., if the agent failed over, or when the > agent was partitioned from the master). > > The master will in its offer operations status handler attempt > to apply operations which became terminal since the last update. At > the same time, the total resources in an `UpdateSlaveMessage` would > already contain the result of applying the operation, and we need to > prevent the master from attempting to apply the same operation twice. > > This patch updates the master handler for `UpdateSlaveMessage` to > transition pending operations which are reported as terminal. For that > we add a new parameter to `updateOperation` to selectively disable > updating of resource state as needed in when called from the > `UpdateSlaveMessage` handler. > > > Diffs > ----- > > src/master/master.cpp 7ed15e4ba2a31c5fe4b8571f645cdca69a3e82f4 > > > Diff: https://reviews.apache.org/r/65072/diff/2/ > > > Testing > ------- > > `make check` > > > Thanks, > > Benjamin Bannier > >
