FYI, I also just reverted the changes to the website that removed the
Jenkins job status.
On 6/2/14, 12:05 AM, Josh Elser wrote:
(fwd back to [email protected])
Thanks for the feedback, Andrew.
-------- Original Message --------
Subject: Re: Overuse of depth=1 on calls to Accumulo's Jenkins jobs'
/api/json
Date: Sun, 1 Jun 2014 10:05:39 -0700
From: Andrew Bayer <[email protected]>
Reply-To: [email protected]
To: [email protected] <[email protected]>
I figured it out - it's manushak.io/streams causing the problems. The
buildStatus link is perfectly fine and can continue to be used, it's
the massive depth=1 queries that end up hosing Jenkins. Thanks,
though!
A.
On Sat, May 31, 2014 at 7:37 PM, Billie Rinaldi <[email protected]> wrote:
The only thing we've found is that we were using links such as this
[1] for
build status on our website. I've removed them, so let us know if the
json
calls don't drop off.
[1]: https://builds.apache.org/job/Accumulo-Master/lastBuild/buildStatus
On Sat, May 31, 2014 at 12:32 PM, Andrew Bayer <[email protected]>
wrote:
Hey Accumulo devs -
I'm noticing a lot of calls to builds.apache.org for the JSON API data
for Accumulo jobs like /job/Accumulo-1.6/api/json?depth=1 - specifying
depth=1 means you're pulling a *LOT* of data, especially considering
that's hitting every job every few minutes. Jenkins hung today and had
a huge number of apparently hung threads trying to populate this data,
and I think these calls may have induced the overall Jenkins UI hang -
please take a look into the more granular control you can get over
depth/tree on https://builds.apache.org/job/Accumulo-1.6/api/ and
consider limiting your queries to just the data you need. Thanks.
A.
