[
https://issues.apache.org/jira/browse/OOZIE-2317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15131559#comment-15131559
]
Robert Kanter commented on OOZIE-2317:
--------------------------------------
We've been discussing internally for Cloudera, and are looking at eventually
moving all Tomcat-based components to using Jetty (for a variety of reasons).
It sounds like Yahoo! is now using standalone Jetty to deploy the WAR file.
While I think we need to continue at least building a WAR file for
compatibility, it might be nice to also support embedded Jetty like Hadoop and
many other projects do. Essentially, you'd be able to do {{oozie-start.sh}}
(maybe with some args or something) and it would start up like a standard Java
program, without a WAR file. This would also make it easier to put jars into
the Oozie server as you wouldn't have to rebuild the WAR file.
Oozie can already run in an embedded Jetty (that's what we do in unit tests),
so I don't think we'd need to do anything too major to support this. Probably
just some maven and shell script changes.
Perhaps we can make some maven profiles and updates to our scripts:
- *default*: current setup where it downloads Tomcat. Though if we keep this
in the long run, we'll need to eventually switch to a newer Tomcat and do any
fixes required to support that.
- *war-only*: current setup where it builds the WAR file, but skips the Tomcat
stuff. This would be useful for users who want to do their own standalone
Tomcat or Jetty.
- *jetty*: setup to run Oozie with an embedded Jetty, the WAR file is not built.
Thoughts?
> 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)
