hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xiao Chen (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-10860) Switch HttpFS to use Jetty
Date Tue, 13 Sep 2016 06:19:21 GMT

     [ https://issues.apache.org/jira/browse/HDFS-10860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Xiao Chen updated HDFS-10860:
-----------------------------
    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.

  was:
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.


> Switch HttpFS to use Jetty
> --------------------------
>
>                 Key: HDFS-10860
>                 URL: https://issues.apache.org/jira/browse/HDFS-10860
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: httpfs
>    Affects Versions: 2.6.0
>            Reporter: John Zhuge
>            Assignee: John Zhuge
>
> 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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org


Mime
View raw message