----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/43753/#review119802 -----------------------------------------------------------
ambari-server/src/main/resources/common-services/HAWQ/2.0.0/alerts.json (line 7) <https://reviews.apache.org/r/43753/#comment181153> We might need to still rephrase it and may be what we had earlier was okay, as there are situation where the status will be mentioned as Not Synchronized but resynchronize will not fix it. Re-sync will not work on all the situations. Once has to remove the standby and re-init it. Refer to the greenplum article, HAWQ should be behaving the same. https://support.pivotal.io/hc/en-us/articles/201157218-gpstate-f-reports-Standby-master-too-far-behind- - bhuvnesh chaudhary On Feb. 19, 2016, 3:33 a.m., Matt wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/43753/ > ----------------------------------------------------------- > > (Updated Feb. 19, 2016, 3:33 a.m.) > > > Review request for Ambari, Alexander Denissov, bhuvnesh chaudhary, Goutam > Tadi, jun aoki, Lav Jain, and Newton Alex. > > > Bugs: AMBARI-15104 > https://issues.apache.org/jira/browse/AMBARI-15104 > > > Repository: ambari > > > Description > ------- > > Update the description for the alert so that the user knows what to do if the > alert is triggered from the description on the alert page > > > Diffs > ----- > > ambari-server/src/main/resources/common-services/HAWQ/2.0.0/alerts.json > 3119a0c > > Diff: https://reviews.apache.org/r/43753/diff/ > > > Testing > ------- > > Manually Tested. Descriptions appears on the alerts page. > > No additional unit tests required. > > > Thanks, > > Matt > >
