Hi all, I think I have a theory for our issues here, and it may have to do with the fact that we are running on a heavily containerized environment (kubernetes). I wanted to consult with the community experts to see what you thought.
The way our container platform works on an update is that it will try to bring up a new container with sling (and our application) against the same mongo database that an original (and still running) container is running against. Now this works fine when the only thing being updated is our application bundle, but it starts encountering problems when several other bundles and configurations are being updated (some removed, some added, some updated). I *think* the core of the problem here is that the bundles and configurations are all stored in the database itself, and two containers with potentially different bundle versions and configurations are attempting to use it simultaneously. If I am right, then our core problem to figure out is how to upgrade a database from one sling version to the next. Let me know what you all think. Regards, Carlos On Tue, Feb 4, 2020 at 7:06 AM Carlos Munoz <camu...@redhat.com> wrote: > Thanks Bertrand! I will continue my fact finding mission here :) > > Regards, > > Carlos > > On Tue, Feb 4, 2020 at 4:31 AM Bertrand Delacretaz <bdelacre...@apache.org> > wrote: > >> Hi, >> >> On Sun, Feb 2, 2020 at 4:50 AM Carlos Munoz <camu...@redhat.com> wrote: >> > ...do configurations from the >> > repoinit files get installed in a specific order with relation to the >> > artifacts?... >> >> The repoinit configs are applied by a single >> SlingRepositoryInitializer [1] service which is implemented by >> org.apache.sling.jcr.repoinit.impl.RepositoryInitializer [2]. >> >> The execution order of the SlingRepositoryInitializer services is >> based on their service rankings [4] and the RepositoryInitializer >> processes its configurations in the order in which they are provided >> by the OSGi framework, sequentially. >> >> All this happens before the SlingRepository service is made available [3] >> >> The logs should help understand what's going on but IIRC it all >> happens in a single thread. >> >> -Bertrand >> >> [1] >> https://sling.apache.org/documentation/bundles/repository-initialization.html >> [2] >> https://github.com/apache/sling-org-apache-sling-jcr-repoinit/blob/master/src/main/java/org/apache/sling/jcr/repoinit/impl/RepositoryInitializer.java >> [3] >> https://github.com/apache/sling-org-apache-sling-jcr-base/blob/e8fe5e004b5af1802bb2a76dbbb583a437f848ee/src/main/java/org/apache/sling/jcr/base/AbstractSlingRepositoryManager.java#L511 >> [4] >> https://github.com/apache/sling-org-apache-sling-jcr-base/blob/e8fe5e004b5af1802bb2a76dbbb583a437f848ee/src/main/java/org/apache/sling/jcr/base/AbstractSlingRepositoryManager.java#L581 >> >>
