[
https://issues.apache.org/jira/browse/HDFS-13885?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16599301#comment-16599301
]
Xiao Chen commented on HDFS-13885:
----------------------------------
Sorry I wasn't clear enough.
I was thinking like:
{code}
LOG.debug("... output stream: 0x{}", Integer.toHexString(dfsos.hashCode())");
{code}
to make the magic number in the log more self explaining.
It would be good to also show in a comment what the logs look like. Running
related unit tests with DEBUG turned on would do. (I looked at it via
{{TestSecureEncryptionZoneWithKMS}} and it looks good, but nice to show this on
jira for reference).
Thanks for working on this, Kitti!
> Improve debugging experience of dfsclient decrypts
> --------------------------------------------------
>
> Key: HDFS-13885
> URL: https://issues.apache.org/jira/browse/HDFS-13885
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: hdfs-client
> Affects Versions: 3.1.0
> Reporter: Kitti Nanasi
> Assignee: Kitti Nanasi
> Priority: Major
> Attachments: HDFS-13885.001.patch, HDFS-13885.002.patch
>
>
> We want to know from the hdfs client log (e.g. hbase RS logs) for each
> CryptoOutputstream, approximately when does the decrypt happen and when does
> the file read happen, to help us rule out or identify hdfs NN / kms / DN
> being slow.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
