> On April 7, 2016, 5:53 a.m., Matt wrote: > > ambari-server/src/main/resources/common-services/HAWQ/2.0.0/package/scripts/hawqstandby.py, > > line 59 > > <https://reviews.apache.org/r/45832/diff/1/?file=1328786#file1328786line59> > > > > Would a service restart be required afer bad hosts (which will get > > ignored) become 'good'?
Not service restart, but once the host is back, the component needs to be started and ambari will push the new configurations. (Regular behavior) - bhuvnesh ----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/45832/#review127562 ----------------------------------------------------------- On April 6, 2016, 7:57 p.m., bhuvnesh chaudhary wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/45832/ > ----------------------------------------------------------- > > (Updated April 6, 2016, 7:57 p.m.) > > > Review request for Ambari, jun aoki, Matt, and Oleksandr Diachenko. > > > Bugs: AMBARI-15743 > https://issues.apache.org/jira/browse/AMBARI-15743 > > > Repository: ambari > > > Description > ------- > > If a HAWQ Component host is down, HAWQ fails during activate standby > operation syncing configuration file to down hosts. > We should use the flag ignore-bad-hosts to exclude the hosts which are > currently marked down so that hawq activate commands does not syncs the file > on bad node. > > > Diffs > ----- > > > ambari-server/src/main/resources/common-services/HAWQ/2.0.0/package/scripts/hawqstandby.py > 2e5dccf > > Diff: https://reviews.apache.org/r/45832/diff/ > > > Testing > ------- > > yes manually. > > > Thanks, > > bhuvnesh chaudhary > >
