On 05/02/11 11:26, Gary Fu wrote:
Hi,
I'm running pgpool2 3.0.1 with replication mode on two postgresql
9.0.4 db servers (updated from 8.4.4). I have the 'replicate_select'
and 'replication_stop_on_mismatch' both set to 'true'.
I just noticed that under psql, if I cancel a long select sql (before
any output displayed), I'll get the following message and the pgpool
failed over. I don't recall this happened with 8.4.4. Can anyone
explain why and how to avoid this ?
[sd3ops1.ops1_admin].sd3ops1> select * from file;
Cancel request sent
ERROR: kind mismatch among backends. Possible last query was: "select
* from file;" kind details are: 0[E: canceling statement due to user
request] 1[D]
HINT: check data consistency among db nodes
server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
The connection to the server was lost. Attempting reset: Succeeded.
Thanks,
Gary
Sorry, forgot to include the log from the pgpool.
2011-05-02 15:12:35 LOG: pid 13181: connection received:
host=172.28.20.139 port=39528
2011-05-02 15:12:35 LOG: pid 13181: cancel_request: canceling backend
pid:2345 key: 159752157
2011-05-02 15:12:35 ERROR: pid 13206: read_kind_from_backend: 1 th kind
D does not match with master or majority connection kind E
2011-05-02 15:12:35 ERROR: pid 13206: kind mismatch among backends.
Possible last query was: "select * from file;" kind details are: 0[E:
canceling statement due to user request] 1[D]
2011-05-02 15:12:35 LOG: pid 13206: notice_backend_error: 1 fail over
request from pid 13206
2011-05-02 15:12:35 LOG: pid 13170: starting degeneration. shutdown
host sd3db2(5432)
2011-05-02 15:12:35 LOG: pid 13170: failover_handler: set new master
node: 0
_______________________________________________
Pgpool-general mailing list
[email protected]
http://pgfoundry.org/mailman/listinfo/pgpool-general
