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 "Shilun Fan (Jira)" <ji...@apache.org> on 2024/01/04 11:23:00 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 ]

Shilun Fan updated HADOOP-16286:
--------------------------------
    Target Version/s: 3.5.0  (was: 3.4.0)

> 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.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org