Return-Path: 
 <user-return-4262-apmail-accumulo-user-archive=accumulo.apache.org@accumulo.apache.org>
X-Original-To: apmail-accumulo-user-archive@www.apache.org
Delivered-To: apmail-accumulo-user-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id F27CB1170A
	for <apmail-accumulo-user-archive@www.apache.org>;
 Fri, 16 May 2014 21:11:33 +0000 (UTC)
Received: (qmail 37381 invoked by uid 500); 16 May 2014 11:54:46 -0000
Delivered-To: apmail-accumulo-user-archive@accumulo.apache.org
Received: (qmail 75440 invoked by uid 500); 16 May 2014 11:48:26 -0000
Mailing-List: contact user-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@accumulo.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@accumulo.apache.org>
List-Post: <mailto:user@accumulo.apache.org>
List-Id: <user.accumulo.apache.org>
Reply-To: user@accumulo.apache.org
Delivered-To: mailing list user@accumulo.apache.org
Received: (qmail 60103 invoked by uid 99); 16 May 2014 11:18:40 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 May 2014 11:18:40 +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 (athena.apache.org: domain of josh.elser@gmail.com
 designates 209.85.216.178 as permitted sender)
Received: from [209.85.216.178] (HELO mail-qc0-f178.google.com)
 (209.85.216.178)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 16 May 2014 00:33:56 +0000
Received: by mail-qc0-f178.google.com with SMTP id l6so3195022qcy.9
        for <user@accumulo.apache.org>; Thu, 15 May 2014 17:33:36 -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:subject:references
         :in-reply-to:content-type:content-transfer-encoding;
        bh=Jbis0C5acwQL03RC61OWqOR+1YpGSzsKxItVAym5540=;
        b=vjEKPIO9XkCEdA0gMtU0hbScl6+JDdymWUVTzDS49wu/YifnVl0g9iDBoOleG7J9tM
         +UHe8IXB7ooRNz+bYEICgfH80vu3yMC86ljFTydhKCcSZ0wu3AxilgJHLQV5EXaKUnS+
         aUykn1hR2cn2QvyC9nEgxXtfnF9ioRnxY/A57Y+FRplkjJifqxwAGAPGLWiTqHn1bp67
         etcxELiSDDGXzyKw1o6FzAffa2GwbtxwSmz+xHDkLzstDN/zv9XZafqzwaH0UzBUUsYo
         A47BvHxHj4ITqfTzsRFIhH5JgQAKawNlZ1Nh3MdZGevMmSbmV2r4NSl1Ip7zKpxCxy8V
         0WWw==
X-Received: by 10.140.82.180 with SMTP id h49mr19806823qgd.84.1400200416018;
        Thu, 15 May 2014 17:33:36 -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
 w2sm10370937qar.21.2014.05.15.17.33.35
        for <multiple recipients>
        (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
        Thu, 15 May 2014 17:33:35 -0700 (PDT)
Message-ID: <53755CDE.20406@gmail.com>
Date: Thu, 15 May 2014 20:33:34 -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: user@accumulo.apache.org, Amit Kapoor <amit@koanect.com>
Subject: Re: Trace log
References: <20140505232854.GA3804@gopher>
 <CADxc9Bmy52gb0aVrdVBsWj7aYuTSoJqj7WzZnMvdn-KoYJ_4KA@mail.gmail.com>
In-Reply-To: 
 <CADxc9Bmy52gb0aVrdVBsWj7aYuTSoJqj7WzZnMvdn-KoYJ_4KA@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

Just to be clear, if the Warning message eventually goes away (should be 
within seconds, maybe minutes), then it's probably just asynch delay.

If a substantial time later you're still getting the warning, that's 
probably a sign that the tracing is used wrong (opened and not closed as 
Eric said).

On 5/7/14, 4:55 PM, Eric Newton wrote:
> Your request can cause some spans to start asynchronously.  Also, spans
> are sent to the tracer asynchronously.  The result is that some of the
> spans may not be recorded by the time that your request finishes.  When
> this happens, children of those requests will exist, but their parent
> spans are not found.  The shell retries a few times with a small wait,
> but it will give up and just print the child spans not knowing what
> started them.
>
> It can also be a bug in the trace logic.  A span that was opened, but
> never closed, for example.
>
> -Eric
>
>
>
> On Mon, May 5, 2014 at 7:28 PM, Amit Kapoor <amit@koanect.com
> <mailto:amit@koanect.com>> wrote:
>
>     Hi folks,
>
>        We are trying to use a variation of IntersectingIterator and
>     turned on trace to help us debug
>        certain performance issues (more on that in a separate email).
>     The trace log page is showing
>        this:
>
>             Warning: the following spans are not rooted!
>        49561cfdf8e1ca5e fa33ce2827eb1141 client:startMultiScan
>        c70795aa7b14de02 f6457a7e4060dec4 client:startMultiScan
>        8ecd2bd6e0342911 751d55532acecba7 client:startMultiScan
>        74a8d66d235750b2 b82977a699403c46 client:startMultiScan
>        ...
>
>        Any hints on what is going on here?
>
>        regards
>
>     Amit
>
>