search

mariadb-corporation / mariadb-columnstore-docker

12 stars 7 forks source link

Persisted volume data truncated on container restart #27

Open dtheodor opened 1 year ago

dtheodor commented 1 year ago

I'm running a single node according to the instructions and cannot figure out how to persist data after the container is recreated. I am providing the directories /var/lib/columnstore and /var/lib/mysql as mounted volumes and see them fill with data, but on recreation columnstore decides to wipe everything, tables and databases.

I see hundreds of log lines like which I suppose is the truncation

docker-mcs1-1  | columnstore/
docker-mcs1-1  | deleting columnstore/data1/000.dir/000.dir/014.dir/119.dir/000.dir/FILE000.cdf
docker-mcs1-1  | deleting columnstore/data1/000.dir/000.dir/014.dir/119.dir/000.dir/
docker-mcs1-1  | deleting columnstore/data1/000.dir/000.dir/014.dir/119.dir/
docker-mcs1-1  | deleting columnstore/data1/000.dir/000.dir/014.dir/118.dir/000.dir/FILE000.cdf
docker-mcs1-1  | deleting columnstore/data1/000.dir/000.dir/014.dir/118.dir/000.dir/
docker-mcs1-1  | deleting columnstore/data1/000.dir/000.dir/014.dir/118.dir/
docker-mcs1-1  | deleting columnstore/data1/000.dir/000.dir/014.dir/117.dir/000.dir/FILE000.cdf
docker-mcs1-1  | deleting columnstore/data1/000.dir/000.dir/014.dir/117.dir/000.dir/
...
stefan1981 commented 1 year ago

I have the same issue. Whenever I shutdown the containers with: docker-compose down and afterwards restart it with: docker-compose up -d all things in the db are gone.