[
https://issues.apache.org/jira/browse/HDFS-16264?focusedWorklogId=662712&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-662712
]
ASF GitHub Bot logged work on HDFS-16264:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 08/Oct/21 13:19
Start Date: 08/Oct/21 13:19
Worklog Time Spent: 10m
Work Description: jianghuazhu opened a new pull request #3533:
URL: https://github.com/apache/hadoop/pull/3533
### Description of PR
When adding block keys, the records come from the specific block pool.
### How was this patch tested?
This is related to logs, and unit testing is less stressful.
--
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.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 662712)
Remaining Estimate: 0h
Time Spent: 10m
> When adding block keys, the records come from the specific Block Pool
> ---------------------------------------------------------------------
>
> Key: HDFS-16264
> URL: https://issues.apache.org/jira/browse/HDFS-16264
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: datanode
> Reporter: JiangHua Zhu
> Assignee: JiangHua Zhu
> Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When adding block keys, some information will be recorded, for example:
> '
> 2021-10-08 20:21:48,844 INFO
> org.apache.hadoop.hdfs.security.token.block.BlockTokenSecretManager: Setting
> block keys
> 2021-10-08 20:21:48,844 INFO
> org.apache.hadoop.hdfs.security.token.block.BlockTokenSecretManager: Setting
> block keys
> '
> Such information is a bit simple, and it is impossible to know which Block
> Pool it comes from. Especially when there are multiple Block Pools, we cannot
> distinguish them.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
