Return-Path: 
 <dev-return-9997-apmail-accumulo-dev-archive=accumulo.apache.org@accumulo.apache.org>
X-Original-To: apmail-accumulo-dev-archive@www.apache.org
Delivered-To: apmail-accumulo-dev-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id EF53911272
	for <apmail-accumulo-dev-archive@www.apache.org>;
 Mon,  2 Jun 2014 04:05:51 +0000 (UTC)
Received: (qmail 32191 invoked by uid 500); 2 Jun 2014 04:05:51 -0000
Delivered-To: apmail-accumulo-dev-archive@accumulo.apache.org
Received: (qmail 32137 invoked by uid 500); 2 Jun 2014 04:05:51 -0000
Mailing-List: contact dev-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@accumulo.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@accumulo.apache.org>
List-Post: <mailto:dev@accumulo.apache.org>
List-Id: <dev.accumulo.apache.org>
Reply-To: dev@accumulo.apache.org
Delivered-To: mailing list dev@accumulo.apache.org
Received: (qmail 32126 invoked by uid 99); 2 Jun 2014 04:05:51 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Jun 2014 04:05:51 +0000
X-ASF-Spam-Status: No, hits=-0.7 required=5.0
	tests=RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of josh.elser@gmail.com designates
 209.85.216.47 as permitted sender)
Received: from [209.85.216.47] (HELO mail-qa0-f47.google.com) (209.85.216.47)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Jun 2014 04:05:48 +0000
Received: by mail-qa0-f47.google.com with SMTP id s7so1970084qap.20
        for <dev@accumulo.apache.org>; Sun, 01 Jun 2014 21:05:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=message-id:date:from:user-agent:mime-version:to:cc:subject
         :references:in-reply-to:content-type:content-transfer-encoding;
        bh=FlUwSTkf3XuDJqN+Kvg3E5N3INg8OYEv5t98vfz4lAA=;
        b=vaAHxviAlweoD2w+4ge8rJlh4b3GAd+BirBbhxconABCy19qzsWYSQW7rCAdc8amNf
         8auFQRKoYYDSqEfqbqlpgViLLhAycwyl/HRpFbZNHb4o80gZm2Oy4x+wJceIufeSZjVb
         VPMrZiaJC7cvXLtGsWiW/dfISxjlb57Rv7emFyeVXNuApLRnRVE3u8CxNAtgGrKS8J6C
         HyhWG5BJ4LgUdNQHDkyQwVcWIv7xqsBTJkK+qNfQdbEPHxgT92+miMfpEZod1rK4Q26n
         G/rRAcjncDGOP1d04iFTCTlVeM6jDwzE+mI+JiWWUtyiruC+AP38KaKWUB0Btc1ZPa7r
         sXRA==
X-Received: by 10.140.88.241 with SMTP id t104mr42730374qgd.29.1401681924157;
        Sun, 01 Jun 2014 21:05:24 -0700 (PDT)
Received: from HW10447.local (pool-71-166-48-47.bltmmd.fios.verizon.net.
 [71.166.48.47])
        by mx.google.com with ESMTPSA id
 s60sm7626524qga.30.2014.06.01.21.05.21
        for <multiple recipients>
        (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
        Sun, 01 Jun 2014 21:05:23 -0700 (PDT)
Message-ID: <538BF801.100@gmail.com>
Date: Mon, 02 Jun 2014 00:05:21 -0400
From: Josh Elser <josh.elser@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9;
 rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: dev <dev@accumulo.apache.org>
CC: andrew.bayer@gmail.com
Subject: Fwd: Re: Overuse of depth=1 on calls to Accumulo's Jenkins jobs'
 /api/json
References: 
 <CAPbPdOYGz2x25RpRJShTNN=iDX+AWoUaXtx7ABb0q_c7+kGycw@mail.gmail.com>
In-Reply-To: 
 <CAPbPdOYGz2x25RpRJShTNN=iDX+AWoUaXtx7ABb0q_c7+kGycw@mail.gmail.com>
X-Forwarded-Message-Id: 
 <CAPbPdOYGz2x25RpRJShTNN=iDX+AWoUaXtx7ABb0q_c7+kGycw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org

(fwd back to dev@a.a.o)

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 <andrew.bayer@gmail.com>
Reply-To: builds@apache.org
To: builds@apache.org <builds@apache.org>

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 <billie@apache.org> 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 <andrew.bayer@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.
>>