----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/49260/#review139564 -----------------------------------------------------------
Ship it! Ship It! - Robert Nettleton On June 27, 2016, 12:42 p.m., Laszlo Puskas wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/49260/ > ----------------------------------------------------------- > > (Updated June 27, 2016, 12:42 p.m.) > > > Review request for Ambari, Daniel Gergely, Oliver Szabo, Robert Nettleton, > and Sandor Magyari. > > > Bugs: AMBARI-17313 > https://issues.apache.org/jira/browse/AMBARI-17313 > > > Repository: ambari > > > Description > ------- > > Problem: > In case services / components are restarted, their desired states are not > changed. As during restart -per definition- services are expected to be in > STARTED state this should be OK, however if the restart is triggered for > services in STOPPED state this causes problems (The UI allows triggering > restart for stopped services). (Eg.: recovery manager doesn't bring them back > to running state) > > Solution: > When assembling the RESTART custom command desired states of affected > services are updated to STARTED. > > > Diffs > ----- > > > ambari-server/src/main/java/org/apache/ambari/server/controller/AmbariCustomCommandExecutionHelper.java > b60592d > > Diff: https://reviews.apache.org/r/49260/diff/ > > > Testing > ------- > > Manually tested on dev-env. > > OK > ---------------------------------------------------------------------- > Total run:1073 > Total errors:0 > Total failures:0 > > > Thanks, > > Laszlo Puskas > >
