topic Re: Alfresco 4.2.X CE with Load Balancing in Alfresco Archive

Alfresco 4.2.X CE with Load Balancing

alfresconewbie — Wed, 16 Jul 2014 10:25:33 GMT

Hi,Hoping someone could clear something up for me;We're looking at the Aflresco 4.2.X Community Edition, I understand the Hazelcast clustering code has been removed, however, what has been mentioned as an option is to run multiple application servers as standalone servers sharing a repository and db

Re: Alfresco 4.2.X CE with Load Balancing

mrogers — Wed, 16 Jul 2014 10:50:00 GMT

The Hazelcast clustering code has never been in community. So it has not been removed.

Perhaps deleted content will still be shown. Perhaps newly added content won't be shown. Perhaps locked content will be shown as unlocked. There will also be a collection of less obvious problems.

The bottom line is that community does not cluster.

Re: Alfresco 4.2.X CE with Load Balancing

alfresconewbie — Wed, 16 Jul 2014 11:27:00 GMT

Hi,

Thanks for your response, albeit a little vague, could you clarify further? is data being persisted/cached at the application layer relevant to whether content has been added/removed/locked?

I'd have expected, if a document is removed from or added to the shared repository, then a repository that is shared between multiple appliction servers would reflect the same on each application server node? the only possible difference would be if some state specific data is persisted on the application servers (which enterprise/hazelcast then syncs).

I should have also said, that our architechure inlcudes an independant Solr server.

Thanks,
AN

Re: Alfresco 4.2.X CE with Load Balancing

alfresconewbie — Thu, 17 Jul 2014 11:36:09 GMT

Any thoughts mrogers?

Regards,
AN

Re: Alfresco 4.2.X CE with Load Balancing

mrogers — Thu, 17 Jul 2014 12:38:47 GMT

Yes it is the cached and ephemeral data that is the problem. The application caches are important for performance. And some ephemeral data (like the application event queue) and lock status is not persisted at all.