That was the only thing I could think of, but the links look like the following, so I wasn't sure they were the culprit. We could get rid of them just in case. https://builds.apache.org/job/Accumulo-Master/lastBuild/buildStatus On May 31, 2014 8:23 PM, "Mike Drob" <md...@mdrob.com> wrote:
> Is it the Jenkins balls under http://accumulo.apache.org/source.html ? I'm > on my phone so I can't actually verify source code, but that is a likely > suspect. > On May 31, 2014 2:01 PM, "Billie Rinaldi" <billie.rina...@gmail.com> > wrote: > > > Anyone know what is causing these queries to builds.a.o? > > > > On Sat, May 31, 2014 at 12:32 PM, Andrew Bayer <andrew.ba...@gmail.com> > > 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. > > > > > >
