Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 29 Nov 2016 18:08:58 +0000 (UTC)
From: "John Zhuge (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <JIRA.13004500.1473743371000.391963.1480442938904@Atlassian.JIRA>
In-Reply-To: <JIRA.13004500.1473743371000@Atlassian.JIRA>
References: <JIRA.13004500.1473743371000@Atlassian.JIRA> <JIRA.13004500.1473743371181@arcas>
Subject: [jira] [Comment Edited] (HADOOP-13597) Switch KMS from Tomcat to
 Jetty
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Tue, 29 Nov 2016 18:09:00 -0000


    [ https://issues.apache.org/jira/browse/HADOOP-13597?page=3Dcom.atlassi=
an.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D15=
704129#comment-15704129 ]=20

John Zhuge edited comment on HADOOP-13597 at 11/29/16 6:08 PM:
---------------------------------------------------------------

Patch 001
- KMSHttpServer based on HttpServer2
- Redirect MiniKMS to KMSHttpServer
- Add kms-default.xml
- Add Jetty properties including SSL properties
- Convert hadoop-kms from war to jar
- Rewrite kms.sh to use Hadoop shell script framework
- Obsolete HTTP admin port for the Tomcat Manager GUI which does not seem t=
o work anyway
- Obsolete {{kms.sh version}} that prints Tomcat version

TESTING DONE
- All hadoop-kms unit tests. MiniKMS equals full KMS.
- Non-secure REST APIs
- Non-secure =E2=80=9Chadoop key=E2=80=9D commands
- SSL REST APIs
- kms.sh run/start/stop/status
- JMX works
- /logs works

TODO
- Set HTTP request header size by env KMS_MAX_HTTP_HEADER_SIZE
- Add static web content /index.html
- More ad-hoc testing
- Integration testing
- Update docs: index.md.vm

TODO in new JIRAs:
- Integrate with Hadoop SSL server configuration
- Full SSL server configuration: includeProtocols/excludeProtocols/includeC=
ipherSuites/excludeCipherSuites, etc.
- Design common Http server configuration. Common properties in =E2=80=9C<m=
odule>-site.xml=E2=80=9D with config prefix, e.g., =E2=80=9Chadoop.kms.=E2=
=80=9D.
- Design HttpServer2 configuration-based builder
- Share web apps code in Common, HDFS, and YARN

My private branch: https://github.com/jzhuge/hadoop/tree/HADOOP-13597.001


was (Author: jzhuge):
Patch 001
- KMSHttpServer based on HttpServer2
- Redirect MiniKMS to KMSHttpServer
- Add kms-default.xml
- Add Jetty properties including SSL properties
- Convert hadoop-kms from war to jar
- Rewrite kms.sh to use Hadoop shell script framework
- Obsolete HTTP admin port for the Tomcat Manager GUI which does not seem t=
o work anyway
- Obsolete {{kms.sh version}} that prints Tomcat version

TESTING DONE
- All hadoop-kms unit tests which exercise the full KMS instead of MiniKMS
- Non-secure REST APIs
- Non-secure =E2=80=9Chadoop key=E2=80=9D commands
- SSL REST APIs
- kms.sh run/start/stop/status

TODO
- Set HTTP request header size by env KMS_MAX_HTTP_HEADER_SIZE
- Add static web content /index.html
- More ad-hoc testing
- Integration testing
- Update docs: index.md.vm

TODO in new JIRAs:
- Integrate with Hadoop SSL server configuration
- Full SSL server configuration: includeProtocols/excludeProtocols/includeC=
ipherSuites/excludeCipherSuites, etc.
- Design common Http server configuration. Common properties in =E2=80=9C<m=
odule>-site.xml=E2=80=9D with config prefix, e.g., =E2=80=9Chadoop.kms.=E2=
=80=9D.
- Design HttpServer2 configuration-based builder
- JMX not working, existing issue
- Share web apps code in Common, HDFS, and YARN

My private branch: https://github.com/jzhuge/hadoop/tree/HADOOP-13597.001

> 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
>
>
> 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 fo=
llowing reasons:
> * Easier migration. Both Tomcat and Jetty are based on {{Servlet Containe=
rs}}, 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: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org