autotest/autotest — Issue #98: pruning autotest results
Author: kparal
Created: 2011-11-30 12:04:25+00:00
State: open

On 11/30/2011 08:52 AM, Kamil Paral wrote:

> Hello Lucas,
>
> I have a question for you about autotest. We are using autotest for scheduling AutoQA tests. At our production server the current test ID is about 240 000. We don't store all the test results on disk, but all the metadata are available in the mysql database. And it starts to slow down noticeably. The web UI is not as responsive as it used to be. Sometimes httpd processes take a lot of memory. "atest job list" became completely unusable, it ends with an error:

The amount of jobs you guys are running are pushing the limits of the
framework, that's good :)

> Operation get_jobs_summary failed:
> OperationalError: (1153, "Got a packet bigger than 'max_allowed_packet' bytes")
>
> Is it possible to prune the database somehow and get rid of the old test metadata (let's say everything older than two months)? Are there some docs somewhere about regarding this task?

We never had to deal with such a massive amount of jobs. For comparison,
for KVM testing we are at 2200. So we will have to create a bug on
autotest and work on an admin script to purge data from specific jobs.
Sorry I don't have anything out ready to help, would you open a ticket
on the github database?

Cheers,

Lucas