Nexus 3 Maven Repo Group Cache Invalidation Persistence


With Nexus OSS 3.52.0-01 using OrientDB, is the cache invalidation timestamp (when you click clear cache) persisted to disk?

We are finding that when our Nexus VM is restarted the previously invalidated cache becomes valid again and we need to clear cache on every restart.

We removed a maven proxy repo from our maven group repo and need to invalidate the group repo cache so it stops reporting it has components from the proxy repo. Looking at the logs, the metadata in our S3 blob store is never deleted (or marked for deletion) but a comparison is made after the blob is fetched against a cache invalidation timestamp.