[ https://issues.apache.org/jira/browse/HADOOP-13597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15704286#comment-15704286 ]
John Zhuge edited comment on HADOOP-13597 at 11/29/16 6:12 AM: --------------------------------------------------------------- Map {{sbin/kms.sh}} to {{bin/hadoop kms}}: | kms.sh run | hadoop kms | | kms.sh start | hadoop kms --daemon start | | kms.sh stop | hadoop kms --daemon stop | | kms.sh status | hadoop kms --daemon status | was (Author: jzhuge): Map {{sbin/kms.sh}} to {{bin/hadoop kms}}: | kms.sh run | hadoop kms | | kms.sh start | hadoop kms --daemon start | | kms.sh stop | hadoop kms --daemon stop | | | hadoop kms --daemon status | > 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 > 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 (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org