If you plan to store 50 million + documents in your repository, you should consider sharding to maximize indexing performance and to enable horizontal scaling to massive content repositories. back to top
You can set up sharding using either manual or dynamic shard registration. We recommend that you use dynamic shard registration because it is easier to implement than manual sharding. back to top
A general rule of thumb is to divide the total number of documents by 50M (million). If you want to increase the query load or support more than 100 concurrent users, then check the memory specifications or the I/O specifications of the installation machine. back to top
This should allow the user to store anywhere between 50 million - 80 million documents in a single shard. For more information, see the Alfresco Platform News and Alfresco 1 billion documents press release with Amazon Aurora.
Alfresco Content Services 6.x uses Alfresco Search and Insight Engine (Solr 6), so sharding is supported with full SSL and non-SSL. Make sure you configure the Solr and SSL settings properly.
For more information, see Installing and configuring Alfresco Search and Insight Engine with mutual TLS using the distribution zip and Installing and configuring Alfresco Search and Insight Engine without mutual TLS using the distribution zip.back to top
Before sharding your Solr index, it is important to consider your query load and the size of your repository. You need to create machines to host Solr. For more information, see Installing and configuring Alfresco Search and Insight Engine. For example, if you need 5 shards, you need to setup those 5 machines, and have Solr instances running on all the 5 machines. Once your machines are ready, you are ready to set up or register shards.
For more information, see Dynamic shard registration.back to top
Yes. After upgrading to Alfresco Content Services 6.0, continue to use the old search index server as before, setup a new sharded Solr server with the rerank template to reindex the data, and finally, switch over to the new sharded index once the indexing is done and the sharded Solr server is up-to-date.
Upgrading from 5.0 with Solr 4 to 6.0 (with zero downtime)
Go to the Solr Admin Web interface at https://localhost:8443/solr/#/alfresco and monitor the value of Approx transactions remaining. If the value is 0, it indicates that the index up-to-date.
back to top
Yes. In a sharded setup, eventual consistency can introduce additional query inconsistencies.
A node can move between shards either by:When this happens, the shards may index at different rates. It is possible to see:
Indexing is eventually consistent. When updates happen at the same time, no inconsistency is seen.back to top