#2299: while pruning changes: too many SQL variables
--------------------------+-----------------------
Reporter: admin@… | Owner:
Type: defect | Status: new
Priority: major | Milestone: undecided
Version: 0.8.5 | Keywords:
--------------------------+-----------------------
After moving a few tasks form one client to another I used
/etc/init/buildmaster reload in order to make the changes take effect,
A few weeks later I realized that the buildmaster process did eat a lot of
mem (approx 3 time of its usual size). looking at the log file I found a
lot of SQL errors (see below) that started 1 day after the changes
described.
The amount of IDs the SQL tries to delete grows from error to error.
After a restart the mem usage was OK again but the errors still show up in
the log!
It would be useful to split (too) large sql queries in single blocks.
--
Ticket URL: <http://trac.buildbot.net/ticket/2299>
Buildbot <http://buildbot.net/>
Buildbot: build/test automation
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Buildbot-commits mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/buildbot-commits
