We don't have any specific instructions for setting up a distributed Roller installation, but it is possible and I know of several sites running distributed. You should be able to setup a system like this without any code changes to Roller:
Web server #1 Roller Referrer turnover task, planet sync tasks (out of process) Web sever #2 Roller Web sever #N Roller File sever / SAN shared by severs #1 through #N for file uploads Database server / cluster shared by #1 though #N for Roller data You might also consider plugging in a distributed cache, such as memcache, for Roller's page cache and Hibernate's L2 cache. But that requires some coding. The only problem with that is Roller's built-in search engine. I'm not sure how well it would work in such a setup, since I haven't tried it. You might have to turn it off. Any Lucene experts around? It would be nice to document this on the wiki. - Dave On 6/14/06, Allen D. Householder <[EMAIL PROTECTED]> wrote:
I've been unable to find anything in the list archives or on the Roller Wiki -- maybe somebody can point me to docs... We have a customer with a high-availability requirement for their Roller installation. The documentation we've seen so far doesn't appear to talk about that at all. I find it difficult to imagine that Sun and IBM are running roller on a single-point-of-failure web host, so how is it actually done? Any advice, pointers, whatever, will be greatly appreciated. Thanks! -allen-
