[
https://issues.apache.org/jira/browse/HDFS-9405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15202145#comment-15202145
]
Xiao Chen commented on HDFS-9405:
---------------------------------
Hey Andrew, that's what I noticed and was trying to do in patch 9, sorry I
didn't mention this in the comments.
Findbugs is not happy with it since we'll be initializing static fields - due
to {{FSDirEncryptionZoneOp#warmUpEdekCache}} being a static method. I'll try
saving the fields instead of startConf on FSNamesystem as you suggested. (BTW,
is the concern on NN memory footprint?)
> 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)
