You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2020/03/17 23:49:00 UTC
[jira] [Updated] (HDDS-3226) Tracing Ozone Manager DB write batch
operations
[ https://issues.apache.org/jira/browse/HDDS-3226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated HDDS-3226:
---------------------------------
Labels: pull-request-available (was: )
> Tracing Ozone Manager DB write batch operations
> ------------------------------------------------
>
> Key: HDDS-3226
> URL: https://issues.apache.org/jira/browse/HDDS-3226
> Project: Hadoop Distributed Data Store
> Issue Type: Improvement
> Affects Versions: 0.5.0
> Reporter: Xiaoyu Yao
> Assignee: Xiaoyu Yao
> Priority: Major
> Labels: pull-request-available
>
> Currently the OM DB write is asynchronously handled in OzoneManagerDoubleBuffer. But the OM response does not have traceID properly populated. As a result, we can't get insight for the DB part of the OM request handling.
> This ticket is opened to add traceID properly so that the addBatch and commitBatch cost of the request can be shown up in properly in Opentracing/Jaeger.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: ozone-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: ozone-issues-help@hadoop.apache.org