You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Chris Trezzo (Jira)" <ji...@apache.org> on 2024/03/01 20:37:00 UTC

[jira] [Updated] (HDFS-17404) Add Namenode info to log message when setting block keys

     [ https://issues.apache.org/jira/browse/HDFS-17404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris Trezzo updated HDFS-17404:
--------------------------------
    Summary: Add Namenode info to log message when setting block keys  (was: Update DN to report which NN has provided the updated block keys)

> Add Namenode info to log message when setting block keys
> --------------------------------------------------------
>
>                 Key: HDFS-17404
>                 URL: https://issues.apache.org/jira/browse/HDFS-17404
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>            Reporter: Joseph Dell'Aringa
>            Priority: Trivial
>              Labels: pull-request-available
>
> 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: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org