Open artntek opened 9 months ago
Ah yes, good catch. I meant to come back to that when I was working on the schema creation stuff. The issue is that the n-shards startup at the same time but only the first needs to create the shared collection. They probably all start to create it at roughly the same time, but only one should. In theory, line 55 of solr-config.sh should catch this:
if ! solr_collection_exists "$SOLR_COLLECTION"; then
but it does not seem to. The other issue is that this only needs to be done on a new PVC where SOLR is starting for the first time, and we need to figure out how to do schema upgrades with exsiting index data in place on the PVC. When I was working on this, I also considered doing some of it in the entrypoint.sh script, which is why we override that from the bitnami default, but IIRC I got rid of all of my changes there and we probably shouldn't override it any longer (so we get the proper bitnami script to run). I looked for a long time for a way to configure the bitnami chart to create our collection rather than their default, but never found a way to configure that through bitnami solr chart values.
Not critical, since the pod automatically restarts, but should be cleaned up at some point to avoid confusion:
Looks like a race condition where one of the solr pods is trying to create the
dataone_index
collection when another one has already created it: