[ 
https://issues.apache.org/jira/browse/HADOOP-13597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15797457#comment-15797457
 ] 

Xiao Chen commented on HADOOP-13597:
------------------------------------

Thanks [~jojochuang] for the review. Good catch, searching for tomcat I can 
also see {{SecureMode.md}} has a mention of tomcat, maybe better changed in the 
httpfs jira though (since that goes in later). Also 1 reference of tomcat in 
{{hadoop-common-project/hadoop-kms/dev-support/findbugsExcludeFile.xml}}, can 
be updated here.

+1 pending those 2 nits though.

Since it's a fairly big and impactful patch, will let it float a few days in 
case other watchers have comments. Plan to commit by Thursday if no objections.

> 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, 
> HADOOP-13597.006.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]

Reply via email to