Hi Everyone, For those of you at the conference - I hope it went well!
I'm still really interested in understanding what should be the standard approach to effectively managing UGC in a clustered Magnolia environment. We’ve used Magnolia for a smaller project and the experience was excellent. Our developers and users both think it’s great. But now I'm in a position where in the next couple of weeks I need to make a decision as to whether or not Magnolia is a suitable product for largish (clustered) Web 2.0 websites that have user generated content (UGC). Think comments, rating, recommendations, etc. I know the latter aren't yet supported but we can extend. I really want to be convinced it is suitable because the general CMS features are great but I’m still searching for the evidence. I've only just read the comments at the bottom of this page: http://documentation.magnolia-cms.com/modules/forum.html Of particular interests are the comments from gjoseph, rah003, and bkraft. Boris says "Magnolia 4.1 allows you repositiry-clusters and supports user-generated content. It includes the first "final" release of both the forum and Public User Registration, so multiple public instances can be handled well.". Does anyone know the “how” to Boris’s comment above? I downloaded a trial version of 4.1 enterprise edition to see if it was an EE only thing but I didn’t see anything that suggested this. I’ve spent the last few hours trying to do exactly as gjoseph has explained by reading http://wiki.apache.org/jackrabbit/Clustering combined with http://wiki.magnolia-cms.com/display/WIKI/MySQL+Persistence. I got it working... Kind of. But it seems to be unreliable. Sometimes content in one cluster will show up instantly in the other. Other times, not at all. When I restart clusters sometimes data entered via one cluster is completely lost even though it was there the entire time the server was up. I get no exceptions in the logs and the Jackrabbit repositories appear to be all setup as proper clusters with journals and all... I even tried clustering just the DMS workspace to simplify things and only activating to one of the public instance... I got the exact same unreliable behaviour. I’ve also found partially clustering a repository (selected workspaces only) causes lots of complications with module installations as pointed out by rah003 in the forum comments above. I’ve also tried clustering the entire public repository but I get similar problems in that if I create a new user in one public instance it doesn’t show up in the other even though they share the same repository. There should be no cache through the admin console either so I don’t expect that to be an issue... Anyway. I hope I’m missing something really basic so if anyone can share their own experiences on getting jackrabbit clustering to work that would be much appreciated! Have a good weekend everyone. Cheers, Brent ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
