You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Xu Shao Hong (Jira)" <ji...@apache.org> on 2021/08/24 04:00:00 UTC
[jira] [Updated] (HDDS-5662) Blank traceId for FsShell command
[ https://issues.apache.org/jira/browse/HDDS-5662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Xu Shao Hong updated HDDS-5662:
-------------------------------
Description:
When debug enabled, the traceId is blank for all FsShell related command.
I found that this is due to lack to registration for tracer.
This is could be simply fixed by registering as how the other tracer register.
!image-2021-08-24-11-54-53-681.png!
was:
The traceId is blank for all FsShell related command.
I found that this is due to lack to registration for tracer.
This is could be simply fixed by registering as how the other tracer register.
!image-2021-08-24-11-54-53-681.png!
> Blank traceId for FsShell command
> ---------------------------------
>
> Key: HDDS-5662
> URL: https://issues.apache.org/jira/browse/HDDS-5662
> Project: Apache Ozone
> Issue Type: Improvement
> Reporter: Xu Shao Hong
> Assignee: Xu Shao Hong
> Priority: Minor
> Attachments: image-2021-08-24-11-54-53-681.png
>
>
> When debug enabled, the traceId is blank for all FsShell related command.
> I found that this is due to lack to registration for tracer.
> This is could be simply fixed by registering as how the other tracer register.
>
> !image-2021-08-24-11-54-53-681.png!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org