t 2:14 AM, JinRong Cai <cai...@gmail.com
> > wrote:
> > Hi Michael,
> >
> > Thanks for your detailed answers.
> >
> > 1, We can see sereral transactions hang in the failover, including:
> > "select 1"
> > "select xxx from ins
ed, was caused by the connection pool.
I am wondering which situration would cause the nova client could not
receive the response?
And which information do I need if dig it further.
Thanks for your help again.
--Jinrong.
在 2017年11月13日星期一 UTC+8上午11:42:13，Mike Bayer写道：
> On Sun, Nov 12, 201
Hi Michael ,
I am using openstack with postgresql which sqlalchemy and oslo_db module
were used.
And there are some problems after my pg database switched over.
Here is my switch over process:
1. nova-conductor(python application) is running with DB connection strings
point to vip , which is
Hi , All,
I am working on the NOVA with sqlalchemy.
And one problem is that I did not find any different with the DB
configuration with max_pool_size/max_overflow:
example: /tmp/nova.conf
[database]
connection =
postgresql://openstack:openstack@:5432/nova?application_name=nova
Hi:
SQLA is used in my python project. And in my code, I have the green thread
used. And the green thread was killed in some of my code. After the the
thread was killed, and the transaction was just began. And the database
connection was still in postgresql server side with status "idle in
