From common-issues-return-154504-archive-asf-public=cust-asf.ponee.io@hadoop.apache.org Fri Jul 6 11:46:04 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id C163D180627 for ; Fri, 6 Jul 2018 11:46:03 +0200 (CEST) Received: (qmail 68364 invoked by uid 500); 6 Jul 2018 09:46:02 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 68353 invoked by uid 99); 6 Jul 2018 09:46:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Jul 2018 09:46:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 145DB1A62D2 for ; Fri, 6 Jul 2018 09:46:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -110.301 X-Spam-Level: X-Spam-Status: No, score=-110.301 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id JAcE8FK6ulsm for ; Fri, 6 Jul 2018 09:46: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 3DA915F4DC for ; Fri, 6 Jul 2018 09:46:01 +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 C0CEDE10D0 for ; Fri, 6 Jul 2018 09:46: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 70968274FA for ; Fri, 6 Jul 2018 09:46:00 +0000 (UTC) Date: Fri, 6 Jul 2018 09:46:00 +0000 (UTC) From: "Steve Loughran (JIRA)" To: common-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HADOOP-15566) Remove HTrace support MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HADOOP-15566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16534634#comment-16534634 ] Steve Loughran commented on HADOOP-15566: ----------------------------------------- Nice screenshots * The HDFS team need to be involved in all discussions w.r.t tracing and wire protocols; I see Anu is watching; [~jnp] should keep an eye on it too * And hbase, eg @stack. I don't see the existing field being reusable unless there's no risk that an htrace client -> opentrace server or opentrace client to htrace-enabled server isn't going to do bad things. Even if we don't know of anything in production, it's part of our [compatibility definition|http://hadoop.apache.org/docs/r3.0.3/hadoop-project-dist/hadoop-common/Compatibility.html#Wire_Protocols]. Making it a new optional field & ignoring the htrace one is the safe route. > Remove HTrace support > --------------------- > > Key: HADOOP-15566 > URL: https://issues.apache.org/jira/browse/HADOOP-15566 > Project: Hadoop Common > Issue Type: Improvement > Components: metrics > Affects Versions: 3.1.0 > Reporter: Todd Lipcon > Priority: Major > Attachments: Screen Shot 2018-06-29 at 11.59.16 AM.png, ss-trace-s3a.png > > > The HTrace incubator project has voted to retire itself and won't be making further releases. The Hadoop project currently has various hooks with HTrace. It seems in some cases (eg HDFS-13702) these hooks have had measurable performance overhead. Given these two factors, I think we should consider removing the HTrace integration. If there is someone willing to do the work, replacing it with OpenTracing might be a better choice since there is an active community. -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: common-issues-help@hadoop.apache.org