[
https://issues.apache.org/jira/browse/HADOOP-16439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16891045#comment-16891045
]
Masatake Iwasaki commented on HADOOP-16439:
-------------------------------------------
> I will spend time today to run the unit tests in other sub components like
> hdfs and yarn. The precommit doesn't check them.
Thanks, [~jojochuang]. We can not rely on Jenkins build to test the bundled
Tomcat since its only in dist tree. unit tests of kms and httpfs are using
Jetty. QA build is just for checking formatting issue of pom.xml.
Attached 001 is upgrading Tomcat to 8.5.43 (latest in 8.5.x). Even in this
case, We don't need much change. It would be better to use 8.5.x because 7.0.x
will be EOL if Tomcat 10 is released.
I manually tested the dist tarball by
* Starting tomcat process can be started by bundled server.xml and
ssl-server.xml for both kms and httpfs.
* creating key by {{hadoop key}} and putting/getting file to/from encryption
zone in pseudo-distributed HDFS.
* putting and getting a file to/from HDFS via httpfs by curl.
> Upgrade bundled Tomcat in branch-2
> ----------------------------------
>
> Key: HADOOP-16439
> URL: https://issues.apache.org/jira/browse/HADOOP-16439
> Project: Hadoop Common
> Issue Type: Improvement
> Components: httpfs, kms
> Reporter: Masatake Iwasaki
> Assignee: Masatake Iwasaki
> Priority: Major
> Attachments: HADOOP-16439-branch-2.000.patch,
> HADOOP-16439-branch-2.001.patch
>
>
> proposed by [~jojochuang] in mailing list:
> {quote}We migrated from Tomcat to Jetty in Hadoop3, because Tomcat 6 went EOL
> in
> 2016. But we did not realize three years after Tomcat 6's EOL, a majority
> of Hadoop users are still in Hadoop 2, and it looks like Hadoop 2 will stay
> alive for another few years.
> Backporting Jetty to Hadoop2 is probably too big of an imcompatibility.
> How about migrating to Tomcat9?
> {quote}
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
