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; } } }

Migration - priming Alfresco Search Services

sunshine

Hello,

We are running a Community 5.2 version using SOLR4 and are in the process of migrating to the equivalent Enterprise version with Alfresco Search Services 1.3 (SOLR6).

To reduce downtime in the indexing process after data migration to the new Enterprise infrastructure, can we point in advance the ASS instance to the Community server and get a headstart in the indexing process ? Or will there be an incompatiblity (license check,...) ?

Thanks in advance.

Have nice day.

Find more posts tagged with

Alfresco Content Services

Accepted answers

ash_saxena10

Also once solr 6 indexing is completed , point the main alfresco to this solr 6 server for searching . and decommission the solr 4 server .

If you approach to point your ASS directly to main alfresco then it will affect the alfresco performance and SOLR 6 indexing performance both . This depends on the how much data is there to be indexed and how much load on the alfresco instance used by business .

All comments

ash_saxena10

why there will be downtime in either of the case . why cant you point your ASS to the alfresco instance for indexing process and once the SOLR 6 index data is ready , point your alfresco to SOLR 6 (ASS ) for searching .

OR the other way , you can setup one more alfresco instance pointing to same repository( alf_data plus DB ) and Alfresco search services pointing to this alfresco, on other server , parallel to the current setup ( which will be up and running ) .
This alfresco instance will be dedicatedly used only for indexing process by Solr and preparing Solr 6 index data .

Once index data is prepared , you can point the actual Alfresco 5.2 to Alfresco search services for searching .
In this way there will be no downtime either you follow this with community or with enterprise .

sunshine

To confirm your first example, what you suggest is we point ASS to the Community instance that is running live in production and prepare the solr6 indexes this way ?

ash_saxena10

I assume you would have separate solr 4 server in Production running on different node where you would have Solr 4 index data .

The better option is to create a replica/clone of solr4 node and remove embedded solr 4 application and solr 4 related data from alfresco ( on cloned node ) and setup ASS on cloned machine pointing to local alfresco for indexing .

ash_saxena10

Also once solr 6 indexing is completed , point the main alfresco to this solr 6 server for searching . and decommission the solr 4 server .