Friday, December 23, 2016

OpenERP configuration

I had a customer with strange issues of OpenERP - the main problem was long life of OpenERP/PostgreSQL sessions. The fix was not hard - using pgBouncer in transaction mode with short server life time (ten minutes).


At December 23, 2016 at 9:57 PM , Blogger Roel said...

And what kind of problems did you have that you solved?

At December 23, 2016 at 10:00 PM , Blogger Pavel Stěhule said...

Although this system has 32GB (and database 4GB) there was not free mem after 1hour. The PostgreSQL processes holds too much memory in free blocks.

At December 25, 2016 at 3:59 PM , Anonymous Michael P. said...

It may be a good idea to explain fully in the post what is the problem, what has been resolved and a detailed method with references to pgbouncer docs. Just telling that there has been a problem does not help :)

At December 25, 2016 at 10:45 PM , Blogger Pavel Stěhule said...

I have not enough informations now, and I know so this article is too short. It is just note - you can use pgbouncer in transaction mode with OpenERP.
The customer originally reported memory leaks of Postgres processes - these processes had more allocated memory than 1GB. I checked it, and I found so this memory was allocated but now it is in free block list. There was not possible to set connection max life on OpenERP - so I had do this fix on Postgres side with pgBouncer.

At February 10, 2017 at 6:43 AM , Anonymous Guido said...

Pavel, do you confirm it was configured in transaction pool mode?
If this is the case, it would be interesting indeed.
I'm trying to make openerp work with pgbouncer in trasaction mode, but I'm still having problems.

At February 10, 2017 at 2:27 PM , Blogger Pavel Stěhule said...

@Guido - I cannot to recheck it now due the customer is from Tasmania and I am from Central Europe and I am not in communication with them - but last message was transactional pool mode and no problems.


Post a Comment

Subscribe to Post Comments [Atom]

<< Home