[
https://issues.apache.org/jira/browse/HADOOP-16972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17084052#comment-17084052
]
Masatake Iwasaki commented on HADOOP-16972:
-------------------------------------------
[~weichiu] The error is the reproducible "Request is a replay (34)". I'm trying
to reproduced the error in a unit test. Using dedicated configuration files
(without hadoop.http.filter.initializers) for KMS like CM worked.
If you have backported HADOOP-16314 and
hadoop.http.filter.initializers=AuthenticationFilterInitializer worked for KMS,
the cause could be on my environment..
> Ignore AuthenticationFilterInitializer for KMSWebServer
> -------------------------------------------------------
>
> Key: HADOOP-16972
> URL: https://issues.apache.org/jira/browse/HADOOP-16972
> Project: Hadoop Common
> Issue Type: Improvement
> Components: kms
> Affects Versions: 3.3.0
> Reporter: Masatake Iwasaki
> Assignee: Masatake Iwasaki
> Priority: Major
>
> KMS does not work if hadoop.http.filter.initializers is set to
> AuthenticationFilterInitializer since KMS uses its own authentication filter.
> This is problematic when KMS is on the same node with other Hadoop services
> and shares core-site.xml with them. The filter initializers configuration
> should be tweaked as done for httpfs in HDFS-14845.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
