Return-Path: X-Original-To: apmail-htrace-dev-archive@minotaur.apache.org Delivered-To: apmail-htrace-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 88DAB184E1 for ; Tue, 9 Jun 2015 02:25:32 +0000 (UTC) Received: (qmail 51412 invoked by uid 500); 9 Jun 2015 02:25:32 -0000 Delivered-To: apmail-htrace-dev-archive@htrace.apache.org Received: (qmail 51348 invoked by uid 500); 9 Jun 2015 02:25:32 -0000 Mailing-List: contact dev-help@htrace.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@htrace.incubator.apache.org Delivered-To: mailing list dev@htrace.incubator.apache.org Received: (qmail 51336 invoked by uid 99); 9 Jun 2015 02:25:32 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Jun 2015 02:25:32 +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 rarecactus@gmail.com designates 74.125.82.51 as permitted sender) Received: from [74.125.82.51] (HELO mail-wg0-f51.google.com) (74.125.82.51) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Jun 2015 02:23:18 +0000 Received: by wgv5 with SMTP id 5so3118234wgv.1 for ; Mon, 08 Jun 2015 19:25:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:content-type:content-transfer-encoding; bh=PnpuJIAAu1XoXv7JJgNa/TSFOegaSpIAjAUXg9YRS30=; b=FGm5eMNIVN7jOjKh+w1ydWdNHe9qIUVlGcMstfNFnQoa0a2huMWFLP3jaV9N+uiH1k xX9DoQprhqumW/ToH1vELyl9ZXAmwwF/nl1FZPmgyT3EAw24d91jC8LoPG3OntoKToJJ sesEc0MGXrBh28hph26y2nRFA5fzOlOhSq57cWQm4vtCBk1JAk0M9JIvQWWmMWoHEBYW BwnaU6itNbjxYrQ9uaUwFGZGYvDpPZNAx5CFG4Wp298kiJrbqxyc/+AVjsmdQNyyeC85 sl6q0jC9/Qf17sN24O9MQ4FKQgvSWlChyufodbcyVSUl8cJqgDD9xyWM7X9gCwND6ZJx 7LPw== MIME-Version: 1.0 X-Received: by 10.180.95.67 with SMTP id di3mr26995424wib.78.1433816706658; Mon, 08 Jun 2015 19:25:06 -0700 (PDT) Sender: rarecactus@gmail.com Received: by 10.194.77.138 with HTTP; Mon, 8 Jun 2015 19:25:06 -0700 (PDT) In-Reply-To: <30481_1433446589_t54JaRb2034378_----To------C.CTo$f3419a38-8d3c-43eb-b24f-b5d49e3ad8ac@alibaba-inc.com> References: <30481_1433446589_t54JaRb2034378_----To------C.CTo$f3419a38-8d3c-43eb-b24f-b5d49e3ad8ac@alibaba-inc.com> Date: Mon, 8 Jun 2015 19:25:06 -0700 X-Google-Sender-Auth: Sv4lpKm0xxDjbpapp0_FFf38ROs Message-ID: Subject: Re: How to deal with "batch" trace? From: Colin McCabe To: dev@htrace.incubator.apache.org, =?UTF-8?B?5p2o5YWL54m5KOmygeWwvCk=?= Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org Hi Kete, Thanks for looking at HTrace! I'm not sure I understand the question completely. What information would you like to trace? HTrace maintains parent/child relationships, but a child can have multiple parents. This may be helpful in the case where you have a span (like flushing a batch) that is logically the child of multiple other spans. best, Colin On Thu, Jun 4, 2015 at 2:10 AM, =E6=9D=A8=E5=85=8B=E7=89=B9(=E9=B2=81=E5=B0= =BC) wrote: > Hi, all: I have a situation when tring to use htrace. Say I have 2 thre= ads, thread-1 takes data and put it into a queue one by one. Since I want t= o trace all these data so i create a Trace&Span for each data and put it in= to queue alone with the data. Thread-2 will cosume the queue periodically, = each time it will take a small batch data from the queue, and process these= data together. How do htrace treat this situation if I want all the data w= ill have a span representing the "process time" even if this "process time"= is a span for the batch. Any idea? Thanks a lot. > YoursKete Yang