Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 881A4200D08 for ; Thu, 7 Sep 2017 00:40:04 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 867FE16128F; Wed, 6 Sep 2017 22:40:04 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id CBF651609E3 for ; Thu, 7 Sep 2017 00:40:03 +0200 (CEST) Received: (qmail 96520 invoked by uid 500); 6 Sep 2017 22:40:02 -0000 Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list hdfs-issues@hadoop.apache.org Received: (qmail 96509 invoked by uid 99); 6 Sep 2017 22:40:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Sep 2017 22:40:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id EC5BC18B599 for ; Wed, 6 Sep 2017 22:40:01 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id KDqGEpr9hX9i for ; Wed, 6 Sep 2017 22:40:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id F3FB85FB9F for ; Wed, 6 Sep 2017 22:40:00 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 735D8E06CF for ; Wed, 6 Sep 2017 22:40:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 2F7CB24147 for ; Wed, 6 Sep 2017 22:40:00 +0000 (UTC) Date: Wed, 6 Sep 2017 22:40:00 +0000 (UTC) From: "Anu Engineer (JIRA)" To: hdfs-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HDFS-11744) Ozone: Implement the trace ID generator MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 06 Sep 2017 22:40:04 -0000 [ https://issues.apache.org/jira/browse/HDFS-11744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16156143#comment-16156143 ] Anu Engineer commented on HDFS-11744: ------------------------------------- [~linyiqun] We have trace ID on each call since the xciever client will fail if we did not have a valid ID. is this JIRA still required? can you please comment? cc: [~msingh] I think it was one of your patches that fixed the issue, care to comment? > Ozone: Implement the trace ID generator > --------------------------------------- > > Key: HDFS-11744 > URL: https://issues.apache.org/jira/browse/HDFS-11744 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: ozone > Affects Versions: HDFS-7240 > Reporter: Yiqun Lin > Assignee: Yiqun Lin > > Currently in ozone, if a client wants to call a container operation command, it requires client to create an unique id. Actually this is not a convenience way, we should provide a specific id generator to help us do this. Also we can keep the original way since sometimes the client wants to use its own traceID in case of error this will be help debugging and tracing. -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org