You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Todd Lipcon (JIRA)" <ji...@apache.org> on 2018/05/23 22:33:00 UTC
[jira] [Commented] (HIVE-19685) OpenTracing support for HMS
[ https://issues.apache.org/jira/browse/HIVE-19685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16488129#comment-16488129 ]
Todd Lipcon commented on HIVE-19685:
------------------------------------
Following is a screenshot of the trace view for the simple integration I've been playing with:
!trace.png!
This makes it very easy to find issues like HIVE-19605 since the slow queries stick out like a sore thumb. It's also helpful for clients of the HMS who have also integrated opentracing -- it's easier to see how much of the total operation time of a slow request can be attributed to the HMS vs other contributing factors.
> OpenTracing support for HMS
> ---------------------------
>
> Key: HIVE-19685
> URL: https://issues.apache.org/jira/browse/HIVE-19685
> Project: Hive
> Issue Type: New Feature
> Components: Metastore
> Reporter: Todd Lipcon
> Priority: Major
> Attachments: trace.png
>
>
> When diagnosing performance of metastore operations it isn't always obvious why something took a long time. Using a tracing framework can provide an end-to-end view of an operation including time spent in dependent systems (eg filesystem operations, RDBMS queries, etc). This JIRA proposes to integrate OpenTracing, which is a vendor-neutral tracing API into the HMS server and client.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)