You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-dev@hadoop.apache.org by "Antony Jay (JIRA)" <ji...@apache.org> on 2018/05/23 00:29:00 UTC
[jira] [Created] (HDFS-13603) Warmup NameNode EDEK caches retries
continuously if there's an invalid key
Antony Jay created HDFS-13603:
---------------------------------
Summary: Warmup NameNode EDEK caches retries continuously if there's an invalid key
Key: HDFS-13603
URL: https://issues.apache.org/jira/browse/HDFS-13603
Project: Hadoop HDFS
Issue Type: Bug
Components: encryption, namenode
Affects Versions: 2.8.0
Reporter: Antony Jay
https://issues.apache.org/jira/browse/HDFS-9405 adds a background thread to pre-warm EDEK cache.
However this fails and retries continuously if key retrieval fails for one encryption zone. In our usecase, we have temporarily removed keys for certain encryption zones. Currently namenode and kms log is filled up with errors related to background thread retrying for ever .
The pre-warm thread should
* Continue to refresh other encryption zones even if it fails for one
* Should retry only if it fails for all encryption zones, which will be the case when kms is down.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org