[
https://issues.apache.org/jira/browse/OOZIE-2317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15606713#comment-15606713
]
Robert Kanter commented on OOZIE-2317:
--------------------------------------
+1 on [~asasvari]'s suggestion.
>From a user's perspective, switching from what we do today with Tomcat to
>using embedded Jetty won't change much because of how Oozie was managing
>Tomcat. The user would still use the same startup script to run Oozie. The
>only things that would change would be that the SSL and other web server
>config properties would all be defined in oozie-site.xml instead of many of
>them being CLI changes. In fact, it would be simpler because you wouldn't
>need to deal with any war repackaging scripts, or special scripts for turning
>on SSL.
Also, the current way Oozie uses Tomcat isn't correct. We download the Tomcat
tarball and Oozie manages it. The correct way to do this would be to use
Tomcat jars from maven and set it up more like what we're doing with embedded
Jetty. But given that we're going to use embedded Jetty, I don't see much
reason to bother also supported embedded Tomcat. Trying to maintain support
for both embedded Jetty and embedded Tomcat is probably not something we want
to do.
We can still support building a WAR file for users who want to deploy Oozie in
their own (not embedded) Tomcat or Jetty. So if someone wants to use Tomcat,
they can deploy a Tomcat server and use the WAR file.
With that in mind, I think we only need one maven profile:
- *(default):* Oozie standalone mode powered by embedded Jetty
- *war:* Oozie builds a WAR file like today, but without downloading Tomcat
[~asasvari] probably has more insight into the easiest way to do this given
he's been working on this a lot more, but off the top of my head, the simplest
way to do this is to probably make the oozie-distro module do the embedded
Jetty stuff, and then have a new WAR packaging module that is off by default.
> Figure out what to do about Tomcat 6 End of Life
> ------------------------------------------------
>
> Key: OOZIE-2317
> URL: https://issues.apache.org/jira/browse/OOZIE-2317
> Project: Oozie
> Issue Type: Bug
> Components: core
> Affects Versions: trunk
> Reporter: Robert Kanter
>
> [Tomcat 6 will be end of life on Dec 31
> 2016.|https://tomcat.apache.org/tomcat-60-eol.html]
> Even though that's a quite a while from now, it's best to stay ahead of
> things, so it would be good if we looked into a plan for this.
> Here are some options:
> # Upgrade to Tomcat 7
> # Upgrade to Tomcat 8
> # Switch to embedded Jetty 9
> I imagine upgrading to Tomcat 7/8 would be the easiest solution. I haven't
> looked into it much, but I imagine the build and deploy process could remain
> relatively the same; though we'd probably have to tweak some config files and
> things. As for which version, Tomcat has [this
> page|https://tomcat.apache.org/whichversion.html] to help.
> Switching to embedded Jetty 9 would require changing the build and deploy
> process, though that might be a good thing given how that can be
> complicated/confusing for users. And I know Tomcat makes things difficult
> for our packaging team in Cloudera. Many other Hadoop projects use embedded
> Jetty as well. We do know that Oozie runs properly in Jetty because our unit
> tests use Jetty.
> As part of this JIRA, the assignee should probably look into more specific
> pros/cons of the options and we should all reach a consensus before moving
> forward.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
