cloning from repo doesn't work properly for bigger databases
Opened this issue · 0 comments
pioro commented
Expected Behavior
When titan is cloning data from remote repo, container is up
and it actually won't see any files in volume during start.
If container is designed to create a new database once starting, it will kick off that process,
once cloning is running in background.
Some files can be created by new database creation and some files will be replicated from remote repository.
Rsync into volume should happen when container is down.
Actual Behavior
Rsync is working when container is up
Steps to Reproduce the Problem
clone any bigger database, so container will have enough time to kick off new database creation process. Tested with an Oracle container