www-builds mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Justin Mason ...@jmason.org>
Subject Re: Hudson restarted
Date Mon, 22 Feb 2010 11:30:44 GMT
On Fri, Feb 19, 2010 at 23:33, Jukka Zitting <jukka.zitting@gmail.com> wrote:
> Hi,
>
> I had to restart Hudson again as it stopped responding to HTTP
> requests. I'm not sure if it was the same OOM issue we saw earlier
> today. This time the log shows only simultaneous EOFExceptions from
> vesta and the hadoop slaves 4, 6 and 8, and then nothing for an hour
> before I forcibly restarted the server.
>
> On Fri, Feb 19, 2010 at 7:04 PM, Justin Mason <jm@jmason.org> wrote:
>> I think we could limit it by a certain number of days.  However, just
>> taking a look now, and it appears most projects have sane limits -- it
>> could be the sheer number of projects that causes trouble.
>
> There are some projects that have quite a few past builds around.
> Here's a quick top-ten count based on counting the builds/*/build.xml
> files for each project:
>
>    745 Cactus
>    674 SpamAssassin-trunk
>    492 Cayenne-trunk
>    358 Chemistry-site
>    340 struts2
>    256 Empire-DB snapshot
>    178 HttpComponents Client
>    172 hupa-trunk
>    168 xwork2
>    146 Hadoop-Patch-h4.grid.sp2.yahoo.net
>
> Only SpamAssassin-trunk and Hadoop-Patch-h4.grid.sp2.yahoo.net have
> discard limits and even they set it pretty high (45 and 21 days). Is
> there any reason to have such a long discard limit? You can always
> explicitly tag builds that you want to keep around to be referenced in
> issue trackers, etc. A few days (say 7 or 10 to be certain) should be
> quite enough to determine whether you need to keep a build around for
> longer or not.

I've now changed SpamAssassin-trunk to keep only 10 days by default
unless the "keep build" feature is used.

--j.

Mime
View raw message