[
https://issues.apache.org/jira/browse/AMBARI-16417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
jun aoki updated AMBARI-16417:
------------------------------
Description:
This is a good-to-have.
When Standby master is down (actually I removed it through API, and it got
deleted but somehow the configuration has the old IP) the hawq alert pops up(,
which is good) but only saying "HAWQSTANDBY is not in sync with HAWQMASTER".
If you take a close look at gp_master_mirroring table, it has more detailed
information. (in this case, connection issue)
{code}
[gpadmin@ip-10-32-38-104 ~]$ psql -d template1 -c "select * from
gp_master_mirroring;"
summary_state | detail_state | log_time |
error_message
------------------+------------------+------------------------+------------------------------------------------------------------------------------------
Not Synchronized | Connection error | 2016-04-12 21:14:23+00 | error received
sending data to standby master: server closed the connection unexpectedly
: This
probably means the server terminated abnormally
: before
or while processing the request.
:
(1 row)
{code}
was:
This is a good-to-have.
When Standby master is down (actually I removed it through API, and it got
deleted but somehow the configuration has the old IP) the hawq alert pops up(,
which is good) but only saying "HAWQSTANDBY is not in sync with HAWQMASTER".
If you take a close look at gp_master_mirroring table, it has more detailed
information. (in this case, connection issue)
```
[gpadmin@ip-10-32-38-104 ~]$ psql -d template1 -c "select * from
gp_master_mirroring;"
summary_state | detail_state | log_time |
error_message
------------------+------------------+------------------------+------------------------------------------------------------------------------------------
Not Synchronized | Connection error | 2016-04-12 21:14:23+00 | error received
sending data to standby master: server closed the connection unexpectedly
: This
probably means the server terminated abnormally
: before
or while processing the request.
:
(1 row)
```
> More information for Standby sync alert
> ---------------------------------------
>
> Key: AMBARI-16417
> URL: https://issues.apache.org/jira/browse/AMBARI-16417
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: trunk
> Reporter: jun aoki
> Assignee: jun aoki
> Priority: Minor
>
> This is a good-to-have.
> When Standby master is down (actually I removed it through API, and it got
> deleted but somehow the configuration has the old IP) the hawq alert pops
> up(, which is good) but only saying "HAWQSTANDBY is not in sync with
> HAWQMASTER".
> If you take a close look at gp_master_mirroring table, it has more detailed
> information. (in this case, connection issue)
> {code}
> [gpadmin@ip-10-32-38-104 ~]$ psql -d template1 -c "select * from
> gp_master_mirroring;"
> summary_state | detail_state | log_time |
> error_message
> ------------------+------------------+------------------------+------------------------------------------------------------------------------------------
> Not Synchronized | Connection error | 2016-04-12 21:14:23+00 | error
> received sending data to standby master: server closed the connection
> unexpectedly
> : This
> probably means the server terminated abnormally
> :
> before or while processing the request.
> :
> (1 row)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
