You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Brahma Reddy Battula (Jira)" <ji...@apache.org> on 2020/04/09 18:51:05 UTC
[jira] [Updated] (HADOOP-16286) Add opentracing into KMS
server/client
[ https://issues.apache.org/jira/browse/HADOOP-16286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brahma Reddy Battula updated HADOOP-16286:
------------------------------------------
Target Version/s: 3.4.0 (was: 3.3.0)
Bulk update: moved all 3.3.0 non-blocker issues, please move back if it is a blocker.
> Add opentracing into KMS server/client
> --------------------------------------
>
> Key: HADOOP-16286
> URL: https://issues.apache.org/jira/browse/HADOOP-16286
> Project: Hadoop Common
> Issue Type: Sub-task
> Reporter: Wei-Chiu Chuang
> Assignee: Wei-Chiu Chuang
> Priority: Major
>
> Recently, while I worked on KMS-o-meter tool, a workload replay tool for KMS, I added opentracing in it and in KMS server/client.(courtesy of Elek, Marton's tracing work in ozone, I simply took a part of it). The ability to understand system performance in such details is unprecedented. We were able to fix a system scalability bug, verify it in record time.
> File this jira to contribute the opentracing code in KMS server/client back to the community.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org