The server can't recover from a database failure
Bug #905257 reported by
Mário Dagot
This bug affects 9 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Odoo Server (MOVED TO GITHUB) |
Fix Released
|
Wishlist
|
OpenERP's Framework R&D | ||
Therp Backports (Deprecated) |
Fix Released
|
Undecided
|
Stefan Rijnhart (Opener) | ||
Server-6.1 |
Fix Released
|
Undecided
|
Stefan Rijnhart (Opener) |
Bug Description
In version 6.0. I'm using 6.0.1.
When the database stops the server can't reconnect to the database, and in this situation two bad things happens:
i) The web client, don't send the correct message to the user. The feedback a user receives is that the username/password is incorrect, this leads to frustration and confusion of users. The correct behavior would be to report for example “server or database not ready”.
ii) After that all openerp servers must be restarted, shutting down all user sessions, imagine a cluster with hundreds of server, thousands of users.
To reproduce just stop, and try to use the web client, start database again, and try to use the web client.
Related branches
lp:~florent.x/openobject-server/trunk-fix-reconnect
- Olivier Dony (Odoo): Approve
- Xavier (Open ERP): Pending requested
-
Diff: 38 lines (+9/-5)1 file modifiedopenerp/sql_db.py (+9/-5)
lp:~florent.x/openobject-server/trunk-bug-905257-fix-reconnect
Rejected
for merging
into
lp:openobject-server
- Florent (community): Approve
- Stephane Wirtel (OpenERP): Pending requested
- OpenERP's Framework R&D: Pending requested
- OpenERP Core Team: Pending requested
-
Diff: 32 lines (+14/-4)1 file modifiedopenerp/sql_db.py (+14/-4)
lp:~florent.x/openobject-server/6.1-bug-905257-fix-reconnect
Rejected
for merging
into
lp:openobject-server/6.1
- OpenERP Core Team: Pending requested
-
Diff: 32 lines (+14/-4)1 file modifiedopenerp/sql_db.py (+14/-4)
lp:~stefan-opener/therp-backports/6.1-bug-905257-fix-reconnect
- Holger Brunn (Therp): Pending requested
-
Diff: 43 lines (+11/-3)2 files modifiedopenerp/sql_db.py (+10/-2)
setup.py (+1/-1)
lp:~openerp-dev/openobject-server/7.0-rstcnx-chs
- OpenERP Core Team: Pending requested
-
Diff: 32 lines (+8/-8)1 file modifiedopenerp/sql_db.py (+8/-8)
description: | updated |
no longer affects: | openobject-client-web |
Changed in therp-backports: | |
status: | New → Fix Committed |
assignee: | nobody → Stefan Rijnhart (Therp) (stefan-therp) |
no longer affects: | ocb-server |
no longer affects: | ocb-server/7.0 |
Changed in therp-backports: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Hello,
This is a known issue, however it is considered minor, as the reliability of the connection to the database is a must in a production environment. I'm sure a cluster with hundreds of servers and thousands of user would have a database connection that is available 100% of the time during business hours. So in most cases, being aware of this limitation is sufficient to properly plan maintenance operations on a production environment (e.g. you should not perform database restarts during business hours, which is simply common sense)
In any case, patches are welcome to improve this, and there's one from the community considered for inclusion at this very moment. I'll link the relevant branch to this bug.
I hope you understand,
Thanks!