hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anu Engineer (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-11744) Ozone: Implement the trace ID generator
Date Wed, 06 Sep 2017 22:40:00 GMT

    [ https://issues.apache.org/jira/browse/HDFS-11744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16156143#comment-16156143

Anu Engineer commented on HDFS-11744:

[~linyiqun] We have trace ID on each call since the xciever client will fail if we did not
have a valid ID. is this JIRA still required? can you please comment? 

cc: [~msingh] I think it was one of your patches that fixed the issue, care to comment? 

> Ozone: Implement the trace ID generator
> ---------------------------------------
>                 Key: HDFS-11744
>                 URL: https://issues.apache.org/jira/browse/HDFS-11744
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: ozone
>    Affects Versions: HDFS-7240
>            Reporter: Yiqun Lin
>            Assignee: Yiqun Lin
> Currently in ozone, if a client wants to call a container operation command, it requires
client to create an unique id. Actually this is not a convenience way, we should provide a
specific id generator to help us do this. Also we can keep the original way since sometimes
the client wants to use its own traceID in case of error this will be help debugging and tracing.

This message was sent by Atlassian JIRA

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

View raw message