hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Zhuge (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-13597) Switch KMS from Tomcat to Jetty
Date Thu, 08 Dec 2016 05:53:58 GMT

     [ 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.003.patch

Patch 003
- Add dependencySets to pom.xml
- Add shell script hadoop_using_envvar and hadoop_mkdir
- Extend hadoop_deprecate_envvar
- Enhance AccessLoggingConfiguration to inherit from Configuration
- Move the configuration keys out of SSLConfig and HttpConfig
- HttpServer2 reads tempDirectory and header sizes from configuration instead of builder

TESTING DONE
- Run “hadoop key list/create/delete/roll” in non-secure and SSL setup
- All KMS unit tests that actually exercise the full-blown KMS
- Script: hadoop kms, hadoop —daemon start|status|stop kms
- Script: kms.sh run|start|status|stop
- /kms/jmx, /kms/logLevel, /kms/conf, /kms/stack, /logs, and /static

TODO
- Update docs: index.md.vm

TODO in new JIRAs:
- Full SSL server configuration: includeProtocols/excludeProtocols/includeCipherSuites/excludeCipherSuites,
etc.
- Share web apps code in Common, HDFS, and YARN

> 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
>
>
> 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: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org


Mime
View raw message