Menu
▾
▴
[Geoserver-users] Geoserver 1.5.3 / PGCluster 1.7 seems to be stuck in deadlocks
|
From: Hari G <ha...@ho...> - 2007-12-27 22:09:41
|
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
=0A=
Hello All -
(this cross-posted to pgcluster-general and geoserver-users lists)
For the last few days I am trying my best to implement a Geoserver that use=
s PGCluster as the backend. With just postgis everything is fine but with P=
GCluster, many database connections gets hung. Sometime I see lot of "idle =
in transaction" threads. I have two physical servers, each running a replic=
ator, load balancer and cluster.
I am not doing any update at this time (I am just using WMS) but when I do =
"select * from pg_locks;" I see 160 rows:
relation | 18577 | 19058 | | | | =
| | | 654004 | 12119 | AccessShareLock | t relation =
| 18577 | 19020 | | | | | =
| | 653938 | 12001 | AccessShareLock | t relation | =
18577 | 18588 | | | | | | =
| 653958 | 12096 | AccessShareLock | t relation | 18577 | =
19020 | | | | | | | 6=
53994 | 12113 | AccessShareLock | t relation | 18577 | 18654 | =
| | | | | | 653980 | 12=
106 | AccessShareLock | t relation | 18577 | 19020 | | =
| | | | | 654191 | 12481 | Acce=
ssShareLock | t relation | 18577 | 19058 | | | =
| | | | 654180 | 12504 | AccessShareLoc=
k | t relation | 18577 | 19020 | | | | =
| | | 654375 | 12900 | AccessShareLock | t rela=
tion | 18577 | 18588 | | | | | =
| | 654191 | 12481 | AccessShareLock | t relation =
| 18577 | 18668 | | | | | | =
| 654540 | 13330 | AccessShareLock | t relation | 18577=
| 18588 | | | | | | | =
654375 | 12900 | AccessShareLock | t relation | 18577 | 1858=
8 | | | | | | | 653938=
| 12001 | AccessShareLock | t transactionid | | | |=
| 654367 | | | | 654367 | 12885 |=
ExclusiveLock | t relation | 18577 | 18588 | | | =
| | | | 653994 | 12113 | AccessSha=
reLock | t transactionid | | | | | 6543=
75 | | | | 654375 | 12900 | ExclusiveLock | t=
relation | 18577 | 19020 | | | | =
| | | 653958 | 12096 | AccessShareLock | t relation =
| 18577 | 19059 | | | | | =
| | 653980 | 12106 | AccessShareLock | t relation | =
18577 | 19062 | | | | | | =
| 654540 | 13330 | AccessShareLock | t transactionid | | =
| | | 654362 | | | | 6=
54362 | 12877 | ExclusiveLock | t transactionid | | | =
| | 654189 | | | | 654189 | 12=
477 | ExclusiveLock | t relation | 18577 | 19059 | | =
| | | | | 654543 | 13298 | Acce=
ssShareLock | t relation | 18577 | 18588 | | | =
| | | | 654190 | 12479 | AccessShareLoc=
k | t relation | 18577 | 19058 | | | | =
| | | 654002 | 12118 | AccessShareLock | t tran=
sactionid | | | | | 653976 | | =
| | 653976 | 12104 | ExclusiveLock | t transactionid =
| | | | | 654004 | | | =
| 654004 | 12119 | ExclusiveLock | t relation | 18577=
| 19020 | | | | | | | =
653982 | 12107 | AccessShareLock | t
Does this look like deadlock to you?=20
I also tried the following:
1. removing the Load balancer and use the cluster directly
2. starting lb and replication servers in Debug mode.
In Debug mode both LB and Replication servers are spitting out a lot of mes=
sages but I saw nothing that is alarming....
I am very new to Pgcluster and hence would like to know if any of you have =
implemented a Geoserver/Pgcluster environment. Any advise would be greatly =
appreciated.
-- Hari Gangadharan
_________________________________________________________________
Get the power of Windows + Web with the new Windows Live.
http://www.windowslive.com?ocid=3DTXT_TAGHM_Wave2_powerofwindows_122007=
|