pgsql: report DISCONNECTED when it isn't about resource-agents

[kskmori]

Matsuo-san,

Any thought on this issue?

elacour
[email protected]
writes:

On a PostgreSQL async streamin replication cluster with 2 nodes. When I stop the slave, then start it after waiting some minutes and some writes on the master, postgresql starts correctly on slave, restoring archive files and finish with this:

LOG: restored log file "000000200000000000000087" from archive
LOG: restored log file "000000200000000000000088" from archive
cp: cannot stat /var/lib/pgsql/tmp/archive/000000200000000000000089': No such file or directory cp: cannot stat/var/lib/pgsql/tmp/archive/00000021.history': No such file or directory
LOG: streaming replication successfully connected to primary

so in fact streaming replication is ok (and I tested writes on master, thay are written on slave).

but crm_mon -A does not reflect this:

Master/Slave Set: ms_pgsql [p_pgsql]
Masters: [ A ]
Slaves: [ B ]
Clone Set: cl_pingd [p_pingd]
Started: [ B A ]

Node Attributes:

• Node A:
  • master-p_pgsql:0 : -INFINITY
  • master-p_pgsql:1 : 1000
  • pgsql-data-status : LATEST
  • pgsql-master-baseline : 0000000061000078
  • pgsql-status : PRI
  • pingd : 400
• Node B:
  • master-p_pgsql:0 : -INFINITY
  • master-p_pgsql:1 : -INFINITY
  • pgsql-data-status : DISCONNECT
  • pgsql-status : HS:alone
  • pingd : 400

---

Reply to this email directly or view it on GitHub:
#104

[t-matsuo]

Hi elacour

Do you use capital hostname ?
The RA doesn't work well with capital hostname.

I'm wirting a patch for this issue.
#105

[elacour]

On Wed, Jun 27, 2012 at 01:16:06AM -0700, Takatoshi MATSUO wrote:

Hi elacour

Do you use capital hostname ?
The RA doesn't work well with capital hostname.

no, it was just added in the report instead of production names that are
lower case.

[t-matsuo]

Please check "select application_name,upper(state),upper(sync_state) from pg_stat_replication;" on A
Can you see as below.

postgres=# select application_name,upper(state),upper(sync_state) from pg_stat_replication;
 application_name |   upper   | upper
------------------+-----------+-------
 B                | STREAMING | ASYNC

[elacour]

On Wed, Jun 27, 2012 at 01:55:33AM -0700, Takatoshi MATSUO wrote:

Please check "select application_name,upper(state),upper(sync_state) from pg_stat_replication;" on A
Can you see as below.

postgres=# select application_name,upper(state),upper(sync_state) from pg_stat_replication;
 application_name |   upper   | upper
------------------+-----------+-------
 B                | STREAMING | ASYNC

Unfortunatly I can't reproduce this bug :(((
(tried three times on the same cluster)

Let's close it and hope it's not going to happen again ;)

And as I'm talking to you, thank you very much for this nice ocf
resource!