[
https://issues.apache.org/jira/browse/HDFS-9405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15202091#comment-15202091
]
Andrew Wang commented on HDFS-9405:
-----------------------------------
Hey Xiao, one last little thing I noticed when I was about to commit this, for
the rest of FSNamesystem we pull the config values out of the conf at
initialization, e.g. lazyPersistFileScrubIntervalSec and so on. Can we do the
same for our two new config keys, to avoid having to keep startConf around?
Thanks.
> Warmup NameNode EDEK caches in background thread
> ------------------------------------------------
>
> Key: HDFS-9405
> URL: https://issues.apache.org/jira/browse/HDFS-9405
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: encryption, namenode
> Affects Versions: 2.7.1
> Reporter: Zhe Zhang
> Assignee: Xiao Chen
> Attachments: HDFS-9405.01.patch, HDFS-9405.02.patch,
> HDFS-9405.03.patch, HDFS-9405.04.patch, HDFS-9405.05.patch,
> HDFS-9405.06.patch, HDFS-9405.07.patch, HDFS-9405.08.patch,
> HDFS-9405.09.patch, HDFS-9405.10.patch, HDFS-9405.11.patch
>
>
> {{generateEncryptedDataEncryptionKey}} involves a non-trivial I/O operation
> to the key provider, which could be slow or cause timeout. It should be done
> as a separate thread so as to return a proper error message to the RPC caller.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
