[ 
https://issues.apache.org/jira/browse/HDDS-2075?focusedWorklogId=310935&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-310935
 ]

ASF GitHub Bot logged work on HDDS-2075:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 11/Sep/19 18:59
            Start Date: 11/Sep/19 18:59
    Worklog Time Spent: 10m 
      Work Description: xiaoyuyao commented on pull request #1415: HDDS-2075. 
Tracing in OzoneManager call is propagated with wrong parent
URL: https://github.com/apache/hadoop/pull/1415
 
 
   
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

    Worklog Id:     (was: 310935)
    Time Spent: 50m  (was: 40m)

> Tracing in OzoneManager call is propagated with wrong parent
> ------------------------------------------------------------
>
>                 Key: HDDS-2075
>                 URL: https://issues.apache.org/jira/browse/HDDS-2075
>             Project: Hadoop Distributed Data Store
>          Issue Type: Sub-task
>            Reporter: Elek, Marton
>            Assignee: Doroszlai, Attila
>            Priority: Major
>              Labels: pull-request-available
>         Attachments: create_bucket-new.png, create_bucket.png
>
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> As you can see in the attached screenshot the OzoneManager.createBucket 
> (server side) tracing information is the children of the freon.createBucket 
> instead of the freon OzoneManagerProtocolPB.submitRequest.
> To avoid confusion the hierarchy should be fixed (Most probably we generate 
> the child span AFTER we already serialized the parent one to the message) 



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to