[
https://issues.apache.org/jira/browse/HDFS-17195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18029136#comment-18029136
]
ASF GitHub Bot commented on HDFS-17195:
---------------------------------------
github-actions[bot] commented on PR #6089:
URL: https://github.com/apache/hadoop/pull/6089#issuecomment-3392652835
We're closing this stale PR because it has been open for 100 days with no
activity. This isn't a judgement on the merit of the PR in any way. It's just a
way of keeping the PR queue manageable.
If you feel like this was a mistake, or you would like to continue working
on it, please feel free to re-open it and ask for a committer to remove the
stale tag and review again.
Thanks all for your contribution.
> NullPointerException thrown in DataXceiver when
> `dfs.encrypt.data.overwrite.downstream.derived.qop` is true
> -----------------------------------------------------------------------------------------------------------
>
> Key: HDFS-17195
> URL: https://issues.apache.org/jira/browse/HDFS-17195
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 3.3.6
> Reporter: ConfX
> Priority: Major
> Labels: pull-request-available
>
> When `dfs.encrypt.data.overwrite.downstream.derived.qop` is true,
> `org.apache.hadoop.hdfs.server.datanode.DataXceiver#writeBlock` crashes with
> NullPointerException. This is because when the configuration is true, the
> block key is being obtained from a `datanode.blockPoolTokenSecretManager`
> that could still be null.
> To reproduce:
> 1. set `dfs.encrypt.data.overwrite.downstream.derived.qop` to true
> 2. run
> `org.apache.hadoop.hdfs.server.datanode.TestDataXceiverBackwardsCompat#testBackwardsCompat`
> We created a PR that provides a fix by making sure the
> blockPoolTokenSecretManager is not null while
> `dfs.encrypt.data.overwrite.downstream.derived.qop` is true.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
