Issue with Shard Creation After Moving Docker Compose Setup - How to Use Existing Local Data?

Support
1

Hi, I’m building Weaviate with Docker and have set the volume to a server path user/weaviate-data. I tried moving my Docker Compose setup to a different location but did not modify the existing configuration, including the cluster name and other settings. When I rebuild and test, the logs from Weaviate show that a new shard is being created in user/weaviate-data.

For example, instead of using the existing user/weaviate/name_of_collection/Qf7ezAZ8ZUPp, it creates a new one like user/weaviate/name_of_collection/jLqfginscazS. Is there a way to use the existing local data?

Thank you in advance!

2

hi @fiellin !!

Welcome to our community! :hugs:

Not sure I understood the steps you went were. :thinking:

Let’s say you have a folder named my_app, with:

  • folder: weaviate_data (mapped to weaviate)
  • file: compose.yaml

You then moved that folder to a different location?

THanks!