[
https://issues.apache.org/jira/browse/HADOOP-13597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Zhuge updated HADOOP-13597:
--------------------------------
Attachment: HADOOP-13597.005.patch
Patch 005
- Set {{HttpServer2.Builder#authFilterConfigurationPrefix}} to integrate with
HttpServer2’s secret provider
- Rename {{AuthenticationFilter#isInitializedByTomcat}} to
{{destroySecretProvider}}
- Update docs: index.md.vm and CommandsManual.md
TESTING DONE
- hadoop key list/create/delete/roll in non-secure and SSL setup
- hadoop —daemon start|stop kms
- kms.sh run
- hadoop daemonlog
- KMS unit tests
- dist-test for module hadoop-common and hadoop-hdfs:
http://dist-test.cloudera.org/job?job_id=hadoop.jzhuge.1481879379.20252, 10
unrelated test failures.
- Shell script unit tests
- /jmx, /logLevel, /conf, /stack, /logs, and /static/index.html
TODO in new JIRAs:
- Update doc CredentialProviderAPI.md and SecureMode.md for both KMS and HttpFS
- HADOOP-13875: Full SSL server configuration:
includeProtocols/excludeProtocols/includeCipherSuites/excludeCipherSuites, etc.
- Share web apps code in Common, HDFS, and YARN
[~aw], [~xiaochen], [~jojochuang], [~rkanter], please review. I believe all
review comments are either addressed or to be followed up in future JIRAs. Let
me know otherwise.
> Switch KMS from Tomcat to Jetty
> -------------------------------
>
> Key: HADOOP-13597
> URL: https://issues.apache.org/jira/browse/HADOOP-13597
> Project: Hadoop Common
> Issue Type: New Feature
> Components: kms
> Affects Versions: 2.6.0
> Reporter: John Zhuge
> Assignee: John Zhuge
> Attachments: HADOOP-13597.001.patch, HADOOP-13597.002.patch,
> HADOOP-13597.003.patch, HADOOP-13597.004.patch, HADOOP-13597.005.patch
>
>
> The Tomcat 6 we are using will reach EOL at the end of 2017. While there are
> other good options, I would propose switching to {{Jetty 9}} for the
> following reasons:
> * Easier migration. Both Tomcat and Jetty are based on {{Servlet
> Containers}}, so we don't have change client code that much. It would require
> more work to switch to {{JAX-RS}}.
> * Well established.
> * Good performance and scalability.
> Other alternatives:
> * Jersey + Grizzly
> * Tomcat 8
> Your opinions will be greatly appreciated.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
