Skip to main content
November 10, 2009
Question

CF Clustering Techniques success/failure?

  • November 10, 2009
  • 1 reply
  • 2388 views

My group is currently looking into restructuring our current CF Archetichture to utilize the clustering technique which is documented here...

http://www.adobe.com/products/jrun/whitepapers/pdf/jr4_clustering_wp.pdf

We are basically trying to find out if anyone has ever  employed such an approach (or something similar) and if so was it indeed successful?

Any suggestions,comments or opinions would be greatly appreciated.

I have attached a diagram which should give you a quick idea of exactly what we are looking to implement.

Thanks

Mike

    This topic has been closed for replies.

    1 reply

    November 19, 2009

    tried it - yes,

    successful - yes,

    similar approach -yes

    make sure u address every error/warning issue in the logs before going live.

    make sure u know ur stick sessions and what u want to do

    make sure ur apps know about cluster environments (esp re above point)

    make sure u can identify which node ran the piece of code (even on production).

    seeing as how it is jrun, don't use the jmc to do anything (very buggy) - similarly cf8/9 cfadmin thingo does it a bit weird, best to do it by hand; at least u then know where everything is.

    also, determine if u want ur clusters to share/ not share any objects on a particular server (ie are they completely independent or what)

    Known Participant
    November 23, 2009

    Ditto to all of the above.

    We've been running CF on JRun since 2003 in distributed mode with IIS/NLB, and clustered

    for CF failover.  Works great.  Over 70 instances of CF with 60 of those clustered.

    November 23, 2009

    Thank you both for the reply. I just want to clarify...

    You have both successfully isolated the webservers from appservers  on there own dedicated machines?

    Im thinking I may have been a little vauge and just want to be sure im on the same page as you two.

    Thanks Again.