Thanks for sharing. I am always interested in how others are doing this stuff. There are always so many ways to do it.
Tony Z On Thu, Mar 3, 2011 at 12:35 AM, pub crawler <[email protected]> wrote: > For what it's worth, we are doing a high availability type solution > with Cherokee in the middle on a hot-hot system (two remote > locations). > > We have a monitoring outsourced DNS provider that requests a URL once > a minute and detects total failure of our main location (should only > occur if that facility were to go offline or all other software layers > in our solution somehow fail to work correctly). When failure occurs > it changes the DNS IP info of our records to the failover location. > > We then have balance (open source common load balancer) running with > main IP on same server as being the preferred site and the IP of the > remote server being failover. This catches any total failure of our > software layer. > > From Balance we head to Varnish which has functionality to cache stuff > (why folks use it). But, it's also scriptable to detect failures and > take action on failure. We run IP of this machine as where traffic > should continue to go, but in case of failures, it has failover IP of > remote site. > > We then go into Cherokee, which has just one balancer backend which > points to another balance instance. > > That balance instance has the IP info for our local application server > and failover info for our remote server. > > It sort of works and is amply fast for our needs. However, Varnish > is a royal pain in a-- to get perfected configuration. It's very > powerful though. > > I have some simple shell scripts for teardowns and start up of the > various piece based on common scenarios. There is the everything > working setup. I have one to eliminate Varnish from the mix. > Another eliminates everything and just puts traffic directly into the > local Cherokee. > > I am looking forward to caching reverse proxy in Cherokee. I *love* > the simplicity of Cherokee and respect it's power. > > So to recap, normal traffic in: > balance --> Varnish --> Cherokee --> balance --> app servers > > If you try this at home do note, balance has some lower > traffic/connection limitations. It won't scale to Varnish or Cherokee > levels, but more than enough for 98% of people. > > HaProxy is on our list to test out also as time allows. > > > On Wed, Mar 2, 2011 at 9:33 PM, Tony Zakula <[email protected]> wrote: >> I would be interested in how that can be done with Cherokee. I have >> seen where Sun web server used as a reverse proxy could be chained >> together in redundant fashion. I have seen where pfsense acting as a >> router can failover to each other and also load balance certain >> things. I am not aware of any other open source server out there that >> can load balance and fail over without doing something very custom >> with Linux and heartbeat. >> >> Tony Z >> >> On Wed, Mar 2, 2011 at 7:49 PM, pub crawler <[email protected]> wrote: >>> The error is a 501 HTTP error being spit out by Cherokee. Unsure if >>> it's the one actually creating the error though. >>> >>> The issue results when I put pound (a load balancer) behind Cherokee >>> and in front of our app server. >>> >>> We swapped pound with balance and the error went away. >>> >>> Arggh! >>> >>> Anyone on the list want to talk about your failover/scalability >>> implementation? Interested in hearing how you are planning for any >>> failure of Cherokee, your app server, etc. >>> >>> Wondering what the most sensible and easiest to manage without >>> breaking functionality like pound did --- is? >>> >>> >>> On Wed, Mar 2, 2011 at 8:28 PM, pub crawler <[email protected]> >>> wrote: >>>> Having an issue with a form post on one of sites. >>>> >>>> When form gets submitted I am getting this in the browser: >>>> >>>> This method may not be used. >>>> >>>> I've stripped everything down so just now Cherokee and our app server >>>> and this persists. >>>> >>>> I am unsure what this error means and if it truly is coming from my >>>> app server or Cherokee. >>>> >>>> Anyone have any insight on this one? >>>> >>> _______________________________________________ >>> Cherokee mailing list >>> [email protected] >>> http://lists.octality.com/listinfo/cherokee >>> >> _______________________________________________ >> Cherokee mailing list >> [email protected] >> http://lists.octality.com/listinfo/cherokee >> > _______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
