Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Fri, 27 Jan 2017 20:42:24 +0000 (UTC)
From: "John Zhuge (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.13004499.1473743333000.21636.1485549744645@Atlassian.JIRA>
In-Reply-To: <JIRA.13004499.1473743333000@Atlassian.JIRA>
References: <JIRA.13004499.1473743333000@Atlassian.JIRA> <JIRA.13004499.1473743333111@jira-lw-us.apache.org>
Subject: [jira] [Updated] (HDFS-10860) Switch HttpFS from Tomcat to Jetty
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 27 Jan 2017 20:42:33 -0000


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

Patch 006
- Use SSLFactory.readSSLConfiguration introduced by HADOOP-13992
- Document use of CredentialProvider API in CredentialProviderAPI.md and ServerSetup.md.vm
- Set TestHttpFSServerWebServer global timeout to 30 seconds

TESTING DONE
- TestHttpFSServerWebServer
- Run {{HTTPFS_HTTP_PORT=1234 hdfs httpfs}} to verify the server is running on port 1234
- Run {{HTTPFS_SSL_KEYSTORE_PASS=abcd hdfs httpfs}} to expect wrong password
- Run {{HTTPFS_SSL_KEYSTORE_FILE=/tmp/tt hdfs httpfs}} to expect invalid keystore path
- HttpFS Bats regression tests https://github.com/jzhuge/hadoop-regression-tests in insecure and ssl mode
- Verify CredentialProviderAPI.html and ServerSetup.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, HDFS-10860.003.patch, HDFS-10860.004.patch, HDFS-10860.005.patch, HDFS-10860.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 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