Datasets missing from Dataverse after GCP instance stop, then start
adkinsrs opened this issue · comments
Hello,
I successfully got Dataverse running on a Google Compute Engine VM using the demostart.sh script. Next, I decided to sandbox a bit by creating some hierarchical Dataverses adding a couple of datasets in various ones. To save on billing costs, I stopped my VM for the weekend. When I started it back up this morning, it seems that the datasets are not visible in any of the Dataverses they were added to. I can still access the various dataset landing pages by clicking the dataset through the administrator notifications but the landing pages do not show in individual Dataverse spaces, nor in filterable facets or searches. Since the dataset information is still being retrieved from Postgres, is there any way that I can restore these on the UI side without having to just re-enter all the information again?
Another side-effect I noticed is that the image for my Dataverse footer is also gone, which I guess is because of the mounted volume to "docroot" in the docker-compose.yml file (which I can adjust)
I think SOLR index isn't persistent. Can you try to reindex everything https://guides.dataverse.org/en/latest/admin/solr-search-index.html
Thanks for the quick response. I will try that
Attempting the "clear and reindex" method, and finally getting it to work after curling within the "dataverse container (found #29)
Interestingly enough, while messing around prior to the "clear and reindex", one of my datasets now shows up (and the other still does not). I am still unsure of how this happened and if I could replicate that.
Thank you so much for the assistance @4tikhonov
@adkinsrs, just put SOLR volume on some persistent GCP volume/bucket, and it should be fine.