[
https://issues.apache.org/jira/browse/HDFS-7580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14264226#comment-14264226
]
Harsh J commented on HDFS-7580:
-------------------------------
Thanks for clarifying that, my bad on assuming its on every call! It seems then
that this issue would occur only during a reconnect to a failing/failed JN.
I wonder then if we should programmatically lower down the KDC timeout to
accommodate the 20s default of JN failures. The retries to KDC are done after
the timeout for a KDC attempt, so a lower timeout of say 5s would perhaps make
more sense than its default of 30s?
> NN -> JN communication should use reusable authentication methods
> -----------------------------------------------------------------
>
> Key: HDFS-7580
> URL: https://issues.apache.org/jira/browse/HDFS-7580
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: journal-node, namenode
> Affects Versions: 2.5.0
> Reporter: Harsh J
>
> It appears that NNs talk to JNs via general SaslRPC in secure mode, causing
> all requests to be carried out with a kerberos authentication. This can cause
> delays and occasionally NN failures if the KDC used does not respond in its
> default timeout period (30s, whereas the QJM writes come with default of 20s).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
