Slide 2.1 has a cluster cache listener implemented that keeps the caches
of each Slide consistent in a load-balanced scenario. When a change
comes into one server it notifies the others which then flush their
cache of references to that object. Refer to the Java doc for the
ClusterCacheRefresher.java for information on how to configure it.
Here's a sample from my Domain.xml file which assumes 3 slide servers in
a cluster.

        <listener
classname="org.apache.slide.cluster.ClusterCacheRefresher">
            <configuration>
                <node local-host="host1"
                    local-port="4444"
                    repository-host="host2"
                    repository-port="8080"
                    repository-protocol="http"
                    repository-domain="/e2dav"
                    base-uri="/"
                    udp="false"
                    />
                <node local-host="host1"
                    local-port="4445"
                    repository-host="host3"
                    repository-port="8080"
                    repository-protocol="http"
                    repository-domain="/e2dav"
                    base-uri="/"
                    udp="false"
                    />
            </configuration>
        </listener>

This is the Domain.xml frag for host #1.  Host #2 and #3 are the other
participants. Port 8080 is the port that the Slide/app servers are
listening on for DAV requests. 

Warwick


> -----Original Message-----
> From: Mohandas, Jeeji [mailto:[EMAIL PROTECTED] 
> Sent: Wednesday, November 09, 2005 10:22 PM
> To: [email protected]
> Subject: Support for multiple instances and load balancing in 
> Slide 2.1
> 
> 
> Hi,
> 
> I had used slide 1.0.16 in a product few years back. Slide 
> worked well in development, but in our deployment 
> configuration Slide was identified as the source of 
> database/file system inconsistencies. The problem was that 
> our deployed systems were running multiple instances of Slide 
> and load-balancing between them. It was concluded at that 
> point of time that Slide was not designed for this and 
> inconsistencies between the instances eventually became 
> committed to the database and file system. Our load testing 
> showed that the single WebDAV server becomes a performance 
> bottleneck, using a large percentage of CPU resources as the 
> load increases. Obviously, the ability to run multiple WebDAV 
> servers would help here. Also, too many files on the slide 
> server, made the system very slow.
> 
> I would like to know if these problems(performance, 
> scalability issues ) are rectified in the latest version(2.1) 
> of Slide. 
> 
> Thanks and Regards,
> Jeeji.
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to