We are using the helm chart for deploying within Minikube. We can see the Alfresco ACS container starting and viewing the logs shows us that it is connecting to the DB container, creating tables and applying patches. However, it fails when it it does the SchemaBootstrap updates which it attempts 24 times. Each time it responds with:
Applied patches detected: 4
Bootstrap marker still present in DB
Another Alfresco Cluster node is updating the DB
The current Alfresco cluster node is waiting for another chance to bootstrap the DB schema.
Once it has tried 24 times it tries to start alfresco again and goes back into this loop.
We know that the retries are configured as part of db.schema.update.lockRetryCount. However, why is the DB locked in the first place when the container tries to start it. We have disabled clustering in the helm chart so what other Alfresco Cluster node is updating the DB.
Any help greatly appreciated.