hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Allen Wittenauer (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-13597) Switch KMS from Tomcat to Jetty
Date Mon, 12 Dec 2016 19:40:58 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-13597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15742931#comment-15742931

Allen Wittenauer commented on HADOOP-13597:

+  hadoop_deprecate_envvar CATALINA_OUT
+  hadoop_deprecate_envvar CATALINA_PID
+  hadoop_deprecate_envvar KMS_ADMIN_PORT
+  hadoop_deprecate_envvar KMS_CATALINA_HOME
+  hadoop_deprecate_envvar KMS_SSL_TRUSTSTORE_PASS

We don't do this anywhere in the scripts. Instead, this is documented in the release notes.
 It's just extra console noise otherwise.

+  hadoop_using_envvar KMS_HOME

This doesn't appear to have actually be configurable by users.  I don't see a reason to add
it now.

+  hadoop_using_envvar KMS_HTTP_PORT
+  hadoop_using_envvar KMS_LOG
+  hadoop_using_envvar KMS_MAX_HTTP_HEADER_SIZE
+  hadoop_using_envvar KMS_MAX_THREADS
+  hadoop_using_envvar KMS_SSL_ENABLED
+  hadoop_using_envvar KMS_SSL_KEYSTORE_FILE
+  hadoop_using_envvar KMS_SSL_KEYSTORE_PASS
+  hadoop_using_envvar KMS_TEMP

I know that branch-2 spit out a bunch of stuff, but it always felt wrong. Is this actually
valuable to anyone that aren't developers? Would \-\-debug be a better usage here? It seems
like a lot of noise on the console that's probably more appropriate for a log file

+  hadoop_using_envvar KMS_SSL_KEYSTORE_PASS


> 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, HADOOP-13597.002.patch, HADOOP-13597.003.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 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

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

View raw message