• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
High Availability Clustering With Alfresco
 

High Availability Clustering With Alfresco

on

  • 25,334 views

http://tinyurl.com/689svq <-- View the recorded webinar. Alfresco has been designed from the ground up to support enterprise scale, mission critical applications. ...

http://tinyurl.com/689svq <-- View the recorded webinar. Alfresco has been designed from the ground up to support enterprise scale, mission critical applications.
In this Webinar we will cover how Alfresco can be deployed to deliver high-availability applications within your organization.

Statistics

Views

Total Views
25,334
Views on SlideShare
25,161
Embed Views
173

Actions

Likes
13
Downloads
1,065
Comments
0

2 Embeds 173

http://www.slideshare.net 171
http://www.redditmedia.com 2

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel

High Availability Clustering With Alfresco High Availability Clustering With Alfresco Presentation Transcript

  • Clustering Alfresco Michael Farman Director of Product Management www.alfresco.com View the recorded webinar here: http:// tinyurl .com/alfresco-cluster
  • Alfresco Server Components
    • Vertical Scalability
      • Note: 1.5GB JVM Limit on 32 bit
    • Multiple Points of Failure
      • Application Server
      • Content and Index Storage
      • Database
    Index & Content Store HTTP/CIFS/NFS/WebDAV/FTP Clients View the recorded webinar here: http:// tinyurl .com/alfresco-cluster Database MySQL Alfresco Server Tomcat EHCache
  • What needs to be clustered?
    • EHCache
      • Single Configuration File Rename
    • Index
      • Note: Each server must have its own index
      • Single Configuration File
      • Only for recovery
    • Content
      • 2 Config Files
        • Define Content Store Locations
        • Declare the Stores
        • Set Replication Type
    • Database
      • Native Database Clustering
    Index & Content Store HTTP/CIFS/NFS/WebDAV/FTP Clients View the recorded webinar here: http:// tinyurl .com/alfresco-cluster Database MySQL Production A Tomcat EHCache
  • Content Clustering Replicating Content Stores
    • Used to synchronise content between content stores
    • Inbound
      • On Read
      • ‘ Pulls’ content from secondary store to primary store
    • Outbound
      • On Write
      • ‘ Push’ content from primary store to secondary store
      • Synchronous (Transactional) or Asynchronous
    Secondary Content Store Primary Content Primary Content Replicating Content Store Replicating Content Store A View the recorded webinar here: http:// tinyurl .com/alfresco-cluster A A A
  • Replicating Content Stores In Action Secondary Content Store Primary Content Primary Content Production A Production B Replicating Content Store Replicating Content Store Note: Production A and B Do not know anything about each other Allows additional servers to be added without reconfiguring A or B Inbound Outbound A 1. Write A 4. Request Content ‘A’ 5. Not Found in Primary 6. Requested from Secondary A 7. Copy stored in Primary A A 2. ‘A’ written to Primary A 3. ‘A’ copied to secondary (sync/async) 8. ‘A’ Delivered Subsequent Requests Served from B Primary Store A
  • Clustered Server - Shared DB and Content
    • √ Horizontal Scalability
    • X Multiple Points of Failure
      • Content Storage*
      • Database
    • Note: Each server needs it’s own local index
    Production A Tomcat EHCache Production B Tomcat EHCache Content Store Index Index * Could be on highly available disk such a SAN storage View the recorded webinar here: http:// tinyurl .com/alfresco-cluster Database MySQL HTTP/CIFS/WebDAV/FTP Clients Load Balancer
  • Clustered Server - Shared Database
    • √ Horizontal Scalability
    • X Single Point of Failure
      • Database
    • Replicating Content Store
      • In and Outbound Replication
    • No need to change config for existing servers when adding additional servers
    Production B Tomcat EHCache Secondary Content Store Index* Index* Primary Content Primary Content Production A Tomcat EHCache Replicating Content Store Replicating Content Store
    • Index recovery component not shown
    • Used to synchronise indexes when necessary e.g. After server restart
    Database MySQL HTTP/CIFS/WebDAV/FTP Clients Load Balancer
  • Database Clustering Master - Slave
    • Use Native DB Clustering Capabilities
    • Specifics Database (and O/S) Dependent
    • Master – Slave
      • Master acts as primary
      • Slave as backup
      • Bring slave online on master failure
        • Scripts
        • O/S Level Clustering
    • Note: Use DB connection pool to avoid Alfresco server restarts
    Database Clustering <- Failover -> DB Slave MySQL JDBC View the recorded webinar here: http:// tinyurl .com/alfresco-cluster DB Master MySQL
  • Database Clustering Master - Master
    • Use Native DB Clustering Capabilities
    • Specifics Database (and O/S) Dependent
    • Master – Master
      • Can be used for distributed deployment
      • Network performance may be a factor
    Database Clustering <- Replication -> DB Master MySQL JDBC JDBC View the recorded webinar here: http:// tinyurl .com/alfresco-cluster DB Master MySQL
  • Configuring a 2 Server Cluster Quick Start Guide
    • Server A
      • Standard Install
      • Configure A’s Primary and the Secondary Store Locations
        • custom-repository.properties
      • Enable Index Tracking
        • index.tracking.cronExpression in custom-repository.properties
      • Enable Content Replication between these locations
        • replicating-content-services-context.xml
          • Define the Shared Content Store
          • Define in/outbound replication between the stores
      • Enable Index Tracking
        • custom-repository.properties
        • index.tracking.cronExpression=0/2 * * * * ? (default entry is 2099 i.e. never)
      • Enable
        • ehcache-custom.xml - Rename the sample
      • Startup
    • Server B
      • Copy A’s Install
      • Configure B’s Primary Content Store – Only required if stores path different
        • repository.properties
        • Note: Secondary Store Location – Same as A
      • Startup with Full Index Recovery – custom-repository.properties
  • Tips & Troubleshooting
    • Starting the server without an index:
      • custom-repository.properties
      • system.bootstrap.config_check.strict=false
    • Always use a fully qualified path to your content and index store locations
      • custom-repository.properties
        • dir.root=c:mystorage
    • Rebuilding indexes
      • You cannot copy indexes from a running server
      • Shutdown and copy or use server generated backup copy
    • System Clocks must be in sync on all servers
      • 1 second by default
    View the recorded webinar here: http:// tinyurl .com/alfresco-cluster
  • More Information
    • Content Community – www.alfresco.com
      • Alfresco High Availability and Clustering Guide
    • http:// wiki .alfresco.com/ wiki / High_Availability_Configuration
    View the recorded webinar here: http:// tinyurl .com/alfresco-cluster
  • View the recorded webinar: http:// tinyurl .com/alfresco-cluster