[
https://issues.apache.org/jira/browse/HADOOP-19094?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17821785#comment-17821785
]
ASF GitHub Bot commented on HADOOP-19094:
-----------------------------------------
Jtdellaringa opened a new pull request, #6598:
URL: https://github.com/apache/hadoop/pull/6598
### Description of PR
Adds namenode index as class variable to BlockTokenSecretManager and logs it
when setting block keys.
### How was this patch tested?
n/a
### For code changes:
- [ x] Does the title or this PR starts with the corresponding JIRA issue id
(e.g. 'HADOOP-17799. Your PR title ...')?
- [ ] Object storage: have the integration tests been executed and the
endpoint declared according to the connector-specific documentation?
- [ ] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [ ] If applicable, have you updated the `LICENSE`, `LICENSE-binary`,
`NOTICE-binary` files?
> Update DN to report which NN has provided the updated block keys
> ----------------------------------------------------------------
>
> Key: HADOOP-19094
> URL: https://issues.apache.org/jira/browse/HADOOP-19094
> Project: Hadoop Common
> Issue Type: Improvement
> Reporter: Joseph Dell'Aringa
> Priority: Trivial
>
> An issue occurred and it was not clear which NN HA instance had failed to
> update the blocks since the current logging in the DN logs doesn't have the
> details. This is a tracking jira to improving logging so we can quickly
> Identify which NN has failed to rotate block key.
> ex log:
> {code:java}
> 2024-01-23 01:32:39,736 INFO
> org.apache.hadoop.hdfs.security.token.block.BlockTokenSecretManager: Setting
> block keys{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
