Details
-
New Feature
-
Status: Resolved
-
Blocker
-
Resolution: Fixed
-
2.6.0
-
None
-
Incompatible change, Reviewed
-
Description
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 to 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.
Attachments
Attachments
Issue Links
- breaks
-
HDFS-11665 HttpFSServerWebServer$deprecateEnv may leak secret
- Resolved
-
HDFS-12114 Consistent HttpFS property names
- Resolved
-
HDFS-12166 Do not deprecate HTTPFS_TEMP
- Resolved
- depends upon
-
HADOOP-13992 KMS should load SSL configuration the same way as SSLFactory
- Resolved
-
HADOOP-13597 Switch KMS from Tomcat to Jetty
- Resolved
-
HADOOP-10075 Update jetty dependency to version 9
- Resolved
-
HADOOP-13990 Document KMS usage of CredentialProvider API
- Resolved
- is depended upon by
-
HADOOP-14367 Remove unused setting from pom.xml
- Resolved
-
HADOOP-14375 Remove tomcat support from hadoop-functions.sh
- Resolved
- is duplicated by
-
HDFS-11176 httpfs.sh run fails due to missing temp dir
- Resolved
-
HDFS-11202 httpfs.sh will not run when temp dir does not exist
- Resolved
- is related to
-
HADOOP-14060 HTTP servlet /logs should require authentication and authorization
- Reopened
- relates to
-
HDFS-11202 httpfs.sh will not run when temp dir does not exist
- Resolved
- supercedes
-
HADOOP-12809 Move to tomcat 8.0.21 to support different passwords for key and keystore on HTTPFS/KMS using SSL
- Resolved
- links to