[Ci-users] Reaping at 12 hrs instead of 2 days

Fri Jan 22 17:39:38 UTC 2016
David Moreau Simard <dms at redhat.com>

+1, I'd like to know if jobs are leaking.

I have something built into my jobs to be able to identify which job a
node belongs to but this might not be the case for every job.

We could *probably* (just thinking out loud here) add a small hook to
node requests in cicoclient that adds an identifier (i.e, echo
$BUILD_URL > /root/.jenkins)

David Moreau Simard
Senior Software Engineer | Openstack RDO

dmsimard = [irc, github, twitter]

On Fri, Jan 22, 2016 at 12:02 PM, James <purpleidea at gmail.com> wrote:
> On Fri, Jan 22, 2016 at 6:26 AM, Karanbir Singh <mail-lists at karan.org> wrote:
>> hi,
>> In the coming days, we are going to start moving towards reaping
>> orphaned machines every 12 hrs. At the moment, machines are reclaimed on
>> the second date change ( ie. if you provisioned at 00:01 on anyday, you
>> get 48 hrs before the machine is reclaimed, or if you provisioned at
>> 23:59, you get 24 hrs ). Going forward, this will reduce to 12 hrs.
>> Looking through the last month worth of reclaimed nodes, it looks like
>> the longest running roles typically finish in under 2 hrs or thereabouts
>> - so 12 hrs should still be plenty of head room. Machines that dont
>> usually returned within 3 hrs + are the ones we almost exclusively end
>> up reclaiming on the timeout.
>> Therefore, this 12 hr timeout should not impact anyone / any jobs. Let
>> me know if thats not the case.
>> Regards
> I agree that this is a good idea, but in addition it would be useful
> to know which users/jobs are not reaping themselves so that they can
> fix their build scripts!
> _______________________________________________
> Ci-users mailing list
> Ci-users at centos.org
> https://lists.centos.org/mailman/listinfo/ci-users