Issue 5435

Title
Wait to get a connection from exhausted pool
Priority
feature
Status
resolved
Nosy list
ced, roundup-bot
Assigned to
ced
Keywords
review

Created on 2016-03-29.12:47:32 by ced, last changed 63 months ago by roundup-bot.

Messages

New changeset fecb48314dc7 by C?dric Krier in branch 'default':
Wait for a connection in PostgreSQL backend
http://hg.tryton.org/trytond/rev/fecb48314dc7
Author: [hidden] (ced) Tryton committer Tryton translator
Date: 2016-03-29.12:49:59
Here is review22911002 which reuse database:retry to limit the waiting loop.
Author: [hidden] (ced) Tryton committer Tryton translator
Date: 2016-03-29.12:47:31
For now, on postgresql backend we use a connection pool with a default limit to 64. But this limit the number of thread the server can answer to also 64 because almost all requests request at least one connection. We can artificially increase this limitation by waiting for an available connection in the postgresql backend. Of course this is not a magical scaling solution and trytond (and postgresql) should still be correctly configured accordingly to the use case. But this solution allow to better resist in case of temporary over usage.
History
Date User Action Args
2016-05-10 10:35:39roundup-botsetstatus: testing -> resolved
nosy: + roundup-bot
messages: + msg25791
2016-03-29 13:00:11reviewbotsetreviews: 22911002
keyword: + review
2016-03-29 12:50:00cedsetstatus: in-progress -> testing
messages: + msg25308
2016-03-29 12:47:32cedcreate

Showing 10 items. Show all history (warning: this could be VERY long)