View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0000466Pgpool-IIGeneralpublic2019-02-16 04:592019-05-21 16:19
Reporternaveedasghar Assigned Topengbo  
PriorityhighSeverityblockReproducibilityalways
Status closedResolutionopen 
Product Version3.7.7 
Summary0000466: Pgpool with RDS Aurora Postgres - prepared statement "_PLAN0x80fb40000" does not exist]
DescriptionI am using pgpool v3.7.2 with RDS aurora, postgres engine version 9.6.8
 
Attached is the pgppool config file.
 
I have one pgpool node installed on EC2 configured with RDS Aurora Postgres Writer and 2 Readers with master_slave_mode ON and load_balance_mode ON.
I am getting lots of error messages when the select statements goes to DB node id: 1 which is reader endpoint
 
Here is the pgpool log message:
Jan 30 18:34:52 ip-10-20-5-46 pgpool: mpsroot mpsdb ec2-54-82-43-225.compute-1.amazonaws.com(44721) idle[28747]: [115-1] 2019-01-30 18:34:52: pid 28747: LOG: DB node id: 1 backend pid: 18291 statement: Parse: SELECT id, memory_total, page_size, memory_free, memory_usage, disk_total_capacity, disk_total, disk_free, disk_used, disk_usage, cpu_usage, node_id FROM "mps_health" ORDER BY id ASC LIMIT 1000000 OFFSET 0
Jan 30 18:34:52 ip-10-20-5-46 pgpool: mpsroot mpsdb ec2-54-82-43-225.compute-1.amazonaws.com(44721) idle[28747]: [116-1] 2019-01-30 18:34:52: pid 28747: LOG: DB node id: 0 backend pid: 13607 statement: D message
Jan 30 18:34:52 ip-10-20-5-46 pgpool: mpsroot mpsdb ec2-54-82-43-225.compute-1.amazonaws.com(44721) idle[28747]: [117-1] 2019-01-30 18:34:52: pid 28747: LOG: DB node id: 1 backend pid: 18291 statement: D message
Jan 30 18:34:52 ip-10-20-5-46 pgpool: mpsroot mpsdb ec2-54-82-43-225.compute-1.amazonaws.com(44721) idle[28747]: [118-1] 2019-01-30 18:34:52: pid 28747: WARNING: packet kind of backend 1 ['t'] does not match with master/majority nodes packet kind ['E']
Jan 30 18:34:52 ip-10-20-5-46 pgpool: mpsroot mpsdb ec2-54-82-43-225.compute-1.amazonaws.com(44721) idle[28747]: [119-1] 2019-01-30 18:34:52: pid 28747: FATAL: failed to read kind from backend
Jan 30 18:34:52 ip-10-20-5-46 pgpool: mpsroot mpsdb ec2-54-82-43-225.compute-1.amazonaws.com(44721) idle[28747]: [119-2] 2019-01-30 18:34:52: pid 28747: DETAIL: kind mismatch among backends. Possible last query was: "Parse: SELECT id, memory_total, page_size, memory_free, memory_usage, disk_total_capacity, disk_total, disk_free, disk_used, disk_usage, cpu_usage, node_id FROM "mps_health" ORDER BY id ASC LIMIT 1000000 OFFSET 0" kind details are: 0[E: prepared statement "_PLAN0x80fb40000" does not exist] 1[t]
Jan 30 18:34:52 ip-10-20-5-46 pgpool: mpsroot mpsdb ec2-54-82-43-225.compute-1.amazonaws.com(44721) idle[28747]: [119-3] 2019-01-30 18:34:52: pid 28747: HINT: check data consistency among db nodes
Jan 30 18:34:52 ip-10-20-5-46 pgpool[28590]: [166-1] 2019-01-30 18:34:52: pid 28590: LOG: child process with pid: 28747 exits with status 512
Jan 30 18:34:52 ip-10-20-5-46 pgpool[28590]: [167-1] 2019-01-30 18:34:52: pid 28590: LOG: fork a new child process with pid: 30973
 
On the client side I am using UnixODBC driver and lots of prepared statements, if I change the pgpool conf and use only RDS writer then its worked fine because all the read and writes goes to writer only but if I use both Writer and Reader where reads go to reader then it started getting the above error message.
 
Is it a version conflict between pgpool and backend postgres version or I am missing anything in the configurations ?
 
Please help.
 
Thanks
NA
TagsNo tags attached.

Activities

naveedasghar

2019-02-16 04:59

reporter  

pgpool.conf (3,700 bytes)

pengbo

2019-02-18 17:33

developer   ~0002392

Is it in an explicit transaction?
Could you provide the debug log of Pgpool-II from begin of the transaction?
To enable debug mode, add "-d" start option to /etc/sysconfig/pgpool.

And could you show me the result of "show pool_nodes"?

Issue History

Date Modified Username Field Change
2019-02-16 04:59 naveedasghar New Issue
2019-02-16 04:59 naveedasghar File Added: pgpool.conf
2019-02-18 17:33 pengbo Note Added: 0002392
2019-04-03 17:07 pengbo Assigned To => pengbo
2019-04-03 17:07 pengbo Status new => assigned
2019-04-08 09:52 pengbo Status assigned => feedback
2019-05-21 16:19 administrator Status feedback => closed