MySQL for backend - Githubissues

diaryniang / ovz-web-panel

Automatically exported from code.google.com/p/ovz-web-panel

Other

0 stars 0 forks source link

MySQL for backend #212

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago

Reason: File blocking of sqlite3 makes the panel useless in a big production 
environment.

Description: Can you please make alternative version of watchdog for mysql 
backend.

Original issue reported on code.google.com by fornex....@gmail.com on 15 Nov 2010 at 8:43

GoogleCodeExporter commented 9 years ago

Original comment by sibprogrammer on 16 Nov 2010 at 8:28

Added labels: Milestone-Release2.0

GoogleCodeExporter commented 9 years ago

Watchdog and panel itself uses connection defined in database.yml config. 
Theoretically its possible to switch to MySQL by modifying configs, loading 
schema and default data. Probably I provide instruction soon how to do it 
manually.

Original comment by sibprogrammer on 16 Nov 2010 at 8:35

GoogleCodeExporter commented 9 years ago

I gave it a go yesterday and there was a problem with watchdog (@sql.execute 
was not working with prepaired statements) and /admin/event-log/list was giving 
an error: Marshal data too short. Everything else was working fine, when I've 
ported sqlite database to mysql.

Original comment by fornex....@gmail.com on 16 Nov 2010 at 8:41

GoogleCodeExporter commented 9 years ago

This issue was updated by revision r771.

MySQL support for watchdog.

Original comment by sibprogrammer on 17 Nov 2010 at 5:41

GoogleCodeExporter commented 9 years ago

This issue was updated by revision r772.

Proper params binding for MySQL.

Original comment by sibprogrammer on 17 Nov 2010 at 6:34

GoogleCodeExporter commented 9 years ago

This issue was updated by revision r773.

Fix problem with data serialization in event log.

Original comment by sibprogrammer on 18 Nov 2010 at 3:39

GoogleCodeExporter commented 9 years ago

If you decide to update from svn, don't forget to delete old records using:
DELETE FROM event_logs;

Original comment by sibprogrammer on 18 Nov 2010 at 3:40

Changed state: Accepted

GoogleCodeExporter commented 9 years ago

thanks a lot for such a rapid fix for mysql. Everything works fine, except that 
watchdog eats 600mb of memory:

 3324 root      18   0  687m 608m 3748 S  0.0 59.4   4:10.02 ruby

is this normal behaviour?

Original comment by fornex....@gmail.com on 18 Nov 2010 at 4:51

GoogleCodeExporter commented 9 years ago

No, it's very strange. On my test machine its size is 33 Mb after 2 hours of 
work.

Original comment by sibprogrammer on 18 Nov 2010 at 4:58

GoogleCodeExporter commented 9 years ago

once in a minute or so, it is also taking 99% of CPU. Watchdog reserves this 
amount of memory at the start. We have at the moment 3 slaves with 60 virtual 
servers in total.

Original comment by fornex....@gmail.com on 18 Nov 2010 at 5:09

GoogleCodeExporter commented 9 years ago

Original comment by sibprogrammer on 19 Nov 2010 at 5:50

Added labels: Milestone-Release1.7
Removed labels: Milestone-Release2.0

GoogleCodeExporter commented 9 years ago

Article about panel database and how to switch to MySQL was create. See 
http://code.google.com/p/ovz-web-panel/wiki/Database

Original comment by sibprogrammer on 20 Nov 2010 at 4:08

Changed state: Fixed