Hello, There is some questions regarding clustering I've never found a clear / consistent answer on.
I hope someone can give me the ultimate answers on my questions.. I've tried to generalize a bit to "broaden" the scope for this, Software Win2003/2008 32/64 bit - IIS6/IIS7 - CF7/8/9 Enterprise - 32bit/64bit Hardware 2-x servers with 1-x jrun/coldfusions instances on each (and 2 nics on each - one connected to the load balancer (via a switch) and one connected to internal network, db server etc (also via a switch)) Hardware load balancer in front of the servers, sticky sessions set on the load balancer x is a number - from 1 to whatever (number of servers and number of instances) Goal: One rock stable high performance ColdFusion cluster with session replication and quick failover when: * JRun/CF instance crashes * Physical server crashes * IIS on server chrashes The setup for the different software configurations is rather similar ("if 32 bit you must pay attention to this", "if 64 bit you must pay attention to that") In any configuration the clustering setup is very similar JRun instances All new CF instances is created from the default CFusion instance which is shut down and "never used" after the setup is done (same goes with JRun Admin Instance) Internal webserver on every CF instance is active with separate port addresses and separate instance names (8300 for admin, 8301 for instance one "cfusion1", 8302 for instance two "cfusion2", 8303 for instance 3 "cfusion3" on physical server #2 etc.) Every CF instance have the remote port (JNDI port) set unique (both server wide and cluster wide) Clustering setup On one server (CFadmin / Instance manager) all remote instances is registered On the same server one cluster is created with round robin / sticky sessions / and replicate sessions set All instances is added to the clusters (for example 6 instances on 3 physical servers on the same subnet) (After this the servers is physically restarted) Connector setup On every physical server the Web Server Configuration Tool is run On every physical server the IIS webserver is configured with this settings: JRun Host: [The server where cluster was created initially] JRun Server: [The cluster name] All IIS websites (The server has multiple websites, hundreds) Configure web server for cf 7/8/9 apps This is where it gets confusing and I'm thinking I must have missed something vital during the setup procedure above. If the server where the cluster was created initially goes down, all instances goes down? Session replication is not very stable (have not tried on 9 yet) Is there something very wrong with the above configuration and setup methods? If so, what/where/why? ;) I've seen descriptions where the same cluster (same cluster name) is created on every physical server, and the connector setup is run against localhost, but that doesn't make sense either.. ? I've been googling for answers on all this many times, since no blog or site I've found have everything covered there are some "black holes" in the descriptions for setting up a cluster. It could also be that the hardware setup is the problem, but I'm hoping for some pointers here before I take a deep look on the HW side of it (which seems to be running just fine on the different setups I've tested) Thanks for any insight on this Helge ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:341163 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm