Closed kainiklas closed 1 year ago
This refers to #70. The MVD components are deployed with in-memory store, meaning that there is no persistence of the data. In other words, data are lost when a container restarts. This is mainly to simplify the deployment of the MVD as deploying a database on top on the MVD components would be cumbersome, and potentially costly (if relying on cloud managed services).
However, feel free to use the extensions delivered by the Eclipse Dataspace Components project to modify the launchers and use persistent storages if you really need it for your own needs. The project provides extensions for PostgreSQL and CosmosDB.
Benjamin.
Bug Report
Describe the Bug
All 3 catalogs are empty after some days without interaction with the MVD.
Expected Behavior
Catalogs are filled all the time. Or an error message like "could not crawl" should be displayed. Maybe a self-healing button should be implemented which can start the crawler manually.
Steps to Reproduce
Context Information