[
https://issues.apache.org/jira/browse/SLIDER-809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14493427#comment-14493427
]
Josh Elser commented on SLIDER-809:
-----------------------------------
Found this gem tonight: [True Zero Downtime HAProxy
Reloads|http://engineeringblog.yelp.com/2015/04/true-zero-downtime-haproxy-reloads.html].
Outlines how Yelp went from about 1s latency with HAProxy to about 20ms latency
in when the backend services are changed (granted, I think we'd be happy with
1s latency :). IMO, one open problem for Slider specifically for supporting
dynamic webservers is how exactly users will transparently use those servers
and not have to deal with all the failure handling going on under the hood by
the AM and YARN. I remember some chatter about a DNS-based registry (as opposed
to ZooKeeper) being suggested which would likely also fit the bill (although
I'm not sure at a technical level how DNS copes with service changes), but my
hunch was that we could wire up something simple with HAProxy given the
information that the AM has about the tomcat containers it's running. If a DNS
registry comes about, then we could investigate going that route instead/too.
> Apache Tomcat App-Package
> -------------------------
>
> Key: SLIDER-809
> URL: https://issues.apache.org/jira/browse/SLIDER-809
> Project: Slider
> Issue Type: New Feature
> Components: app-package
> Reporter: Josh Elser
> Assignee: Josh Elser
> Fix For: Slider 0.80
>
>
> I started working on an app-package for Tomcat.
> https://github.com/apache/incubator-slider/tree/feature/SLIDER-809-tomcat-app-package/app-packages/tomcat
> Some things that need to happen for a generally usable app-package:
> * Maven module in slider for the code
> * -Template for server.xml -- notably the port to listen on and other options-
> * Reference external WAR file
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
