acs-deployment Use Statefulset instead of deployment for Solr

Hi,

shouldn't solr be deployed using a statefulset instead of a deployment in a multi master configuration because the replicas cannot share the same volume?

All replicas but one fails with the current helm chart when I set the replica count to a value > 1.

Regards, Torsten

Jul 19 '19 13:07 torstenwerner

@Marina-Alfresco this issue should be moved to https://github.com/Alfresco/acs-deployment

Oct 20 '20 13:10 aborroy

The repository Deployment should probably also be change to a StatefulSet

Nov 26 '20 14:11 andreaskring

Tracked internally via https://alfresco.atlassian.net/browse/OPSEXP-800

Mar 01 '21 15:03 gavincornwell

As far as I can see it, the repository don't have to be a statefulSet (at least when your contentstore is on a RWX volume), but activeMQ should probably be a statefulSet aswell.

Mar 17 '21 08:03 ariksidney

Following the recent updates on both Ansible playbook and Helm charts I'm closing this issue as we don't recommend using Solr workload in-cluster so we prefer avoiding to provide features such as HA for Solr within Helm as it would create confusion on the relevance of runnign Solr for production workload in kubernetes. See https://github.com/Alfresco/acs-deployment/blob/master/docs/helm/examples/search-services.md

Jan 17 '23 20:01 alxgomz