Hi list,
I want to raise a problem with our 1.3 production system and ask if we
will run into this in 1.4 too.
After nearly a year in production and around 750 recordings our database
got extremly large ( > 2GB). The reason is mainly that the table
job_arguments got very large (>1.7GB). This results in a mysql database
that is running on 100% load permanently.
We reported this in MH-9342 [1] and I've seen that Stephen Marquard has
report the same in MH-9031 as I just noticed.
I did my testing that I can delete the job_arguments without doing any
harm, and Tobias seems to be on the same opinon in his comment on MH-9031.
So my question would be: is this addressed or even fixed in 1.4 that we
delete finished jobs in the DB? This bug won't come up in our QA
testing, as we will not process several hundred jobs there. But it will
be a serious problem for any production system, although there is an
easy fix for this.
Thanks
Rüdiger
[1] http://opencast.jira.com/browse/MH-9342
[2] http://opencast.jira.com/browse/MH-9031
--
________________________________________________
Rüdiger Rolf, M.A.
Universität Osnabrück - Zentrum virtUOS
Heger-Tor-Wall 12, 49069 Osnabrück
Telefon: (0541) 969-6511 - Fax: (0541) 969-16511
E-Mail: [email protected]
Internet: www.virtuos.uni-osnabrueck.de
_______________________________________________
Matterhorn mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn
To unsubscribe please email
[email protected]
_______________________________________________
