Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cloning from repo doesn't work properly for bigger databases #163

Open
pioro opened this issue Mar 2, 2020 · 0 comments
Open

cloning from repo doesn't work properly for bigger databases #163

pioro opened this issue Mar 2, 2020 · 0 comments
Labels
Type: Bug Something isn't working

Comments

@pioro
Copy link

pioro commented Mar 2, 2020

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

@pioro pioro added the Type: Bug Something isn't working label Mar 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant