[
https://issues.apache.org/jira/browse/HDFS-9853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15163868#comment-15163868
]
Anu Engineer commented on HDFS-9853:
------------------------------------
I was not sure that Htrace IDs are used across the board. So even though Ozone
front-end uses UUIDs and hence 128 bit trace IDs, I did not want to bake that
assumption in the transport / protocol layer. Once we enable HTrace in Ozone I
would think we can easily switch over.
As for why the responses have traceID, it allows logging at transport layer and
easy correlation of these packets instead of relying on a temporal ordering. It
is much easier to write log parsing tools with explicit trace IDs, especially
when we are in the development phase.
An auxiliary benefit (which we don't intend to leverage) is to ability to
return multiple responses for a request as well as easier multi-threading code
on the client side.
> Ozone: Add container definitions
> --------------------------------
>
> Key: HDFS-9853
> URL: https://issues.apache.org/jira/browse/HDFS-9853
> Project: Hadoop HDFS
> Issue Type: Sub-task
> Reporter: Anu Engineer
> Assignee: Anu Engineer
> Attachments: HDFS-9853-HDFS-7240.001.patch,
> HDFS-9853-HDFS-7240.002.patch
>
>
> This patch introduces protoc definitions that operate against the container
> on a datanode.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
