Opened on 03/20/2015 at 03:45:44 AM
Closed on 06/15/2015 at 08:15:38 AM
#2184 closed defect (incomplete)
Configure Rietveld to use a more sophisticated RDBMS
| Reported by: | matze | Assignee: | |
|---|---|---|---|
| Priority: | P3 | Milestone: | |
| Module: | Infrastructure | Keywords: | |
| Cc: | trev, fhd, fred | Blocked By: | |
| Blocking: | #2182 | Platform: | Unknown |
| Ready: | yes | Confidential: | no |
| Tester: | Verified working: | no | |
| Review URL(s): | |||
Description
The current setup of Rietveld in modules/rietveld uses sqlite3 as DATABASE_ENGINE (settings.py). This is not sufficient, SQLite is not optimized for multiple, concurrent access and would thus be way to slow in production (if it even works).
In addition, it causes e.g. some manage.py commands to fail from time to time when the daemon is running in the background. This includes our own provisioning process, so re-provisioning the host currently fails from time to time - unless the daemon has been manually stopped before.
There are some other issues as well, but altogether it's quite obvious that we need to set up a more sophisticated database system. We have both PostgreSQL and MySQL integrated with our Puppet code already, and the underlying Framework can deal with any of them, so either one should do fine.
Attachments (0)
Change History (3)
comment:1 Changed on 03/20/2015 at 03:50:01 AM by matze
- Component changed from Unknown to Infrastructure
comment:2 Changed on 04/15/2015 at 09:08:02 PM by matze
- Cc trev fhd fred added
- Review URL(s) modified (diff)
- Status changed from new to reviewing
- Verified working unset
comment:3 Changed on 06/15/2015 at 08:15:38 AM by matze
- Resolution set to incomplete
- Status changed from reviewing to closed
This ticket is obsolete since we do not use gae2django any more.