[
https://issues.apache.org/jira/browse/HDFS-10860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Zhuge updated HDFS-10860:
------------------------------
Attachment: HDFS-10860.002.patch
Patch 002
- Update doc index.md, ServerSetup.md.vm, and HDFSCommands.md
- Set {{HttpServer2.Builder#authFilterConfigurationPrefix}} to integrate with
HttpServer2’s secret provider
TESTING DONE
- hdfs dfs -ls webhdfs://localhost:14000/
- hdfs dfs -ls swebhdfs://localhost:14000/“ in SSL mode
- hdfs https, hdfs —daemon start|status|stop httpfs
- httpfs.sh run|start|status|stop
- hadoop daemonlog
- HttpFS unit tests
- dist-test nadoop-common and hadoop-hdfs:
http://dist-test.cloudera.org/job?job_id=hadoop.jzhuge.1481879379.20252, 10
unrelated test failures.
- /jmx, /logLevel, /conf, /stack, /logs, and /static/index.html
> Switch HttpFS from Tomcat to Jetty
> ----------------------------------
>
> Key: HDFS-10860
> URL: https://issues.apache.org/jira/browse/HDFS-10860
> Project: Hadoop HDFS
> Issue Type: New Feature
> Components: httpfs
> Affects Versions: 2.6.0
> Reporter: John Zhuge
> Assignee: John Zhuge
> Attachments: HDFS-10860.001.patch, HDFS-10860.002.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 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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
