[
https://issues.apache.org/jira/browse/HDFS-13603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Antony Jay updated HDFS-13603:
--
Description:
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 warmup 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.
was:
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.
Summary: Warmup NameNode EDEK thread retries continuously if there's an
invalid key (was: Warmup NameNode EDEK caches retries continuously if there's
an invalid key )
> Warmup NameNode EDEK thread 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
>Priority: Major
>
> 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 warmup 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-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
