nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Veritas Clustered File System compatibility

ethanadams

I'm thinking of using a Veritas clustered file system for the content store that will be mounted by 2 alfresco respository applications running on 2 different machines, using the same database. I think that this would remove the need for replicating the content store and search indexes.

Anyone know of reasons this wouldn't work? Can the search indexes be shared by the 2 alfresco instances.

Find more posts tagged with

Comments

andy

Hi

The search indexes can not be shared between servers at the moment.
Content is fine.
You would have to use our replication.

As it happens, I am working on fixing that, so many repositories can use *the same* indexes.

In any case file locking is required. Is this suported by the Veritas clustered file system? Otherwise a shared lock of some sort would be required during replication. Othyerwise, what happens when both modify the same file?

In the medium term we are trying to make this easier.

Regards

Andy

ethanadams

Thanks for the reply. Just some followup…

So, are you saying I can have one clustered disk, that is mounted by both servers (A and

at let's say /alf_data

Then properties on A would be:
dir.root=/alf_data
dir.contentstore=${dir.root}/contentstore
dir.contentstore.deleted=${dir.root}/contentstore.deleted
dir.indexes=${dir.root}/lucene-indexes-A
dir.indexes.lock=${dir.indexes}/locks-A

And B would be:
dir.root=/alf_data
dir.contentstore=${dir.root}/contentstore
dir.contentstore.deleted=${dir.root}/contentstore.deleted
dir.indexes=${dir.root}/lucene-indexes-A
dir.indexes.lock=${dir.indexes}/locks-A

Then I setup replication for the indexes?

Or, are you saying I need /alf_data-A and /alf_data-B and replicate content and indexes?

andy

Hi

As things stand, each repository must have its own independant index.
Sharing the same index is work in progress.

Regards

Andy

ethanadams

Ok I think I got it on the Lucene stuff.

Still unclear on what you are saying about the content store. are you saying that dir.contentstore=/veritas_disk/contentstore can be the shared by A and B (NO replication)?

Or are you saying I need a dir.contentstore=/veritas_disk/contentstore-A and dir.contentstore=/veritas_disk/contentstore-B and then replicate between them?

andy

Hi

For the content store you could use both of the configurations you describe.

Regards

Andy

msmith

Andy: Regarding many repositories using the same Lucene indexes: did this feature make it into the product yet?