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

after application of MR 188, jobs always starting after DLE restart #22

Open
terem42 opened this issue Oct 13, 2021 · 0 comments
Open

Comments

@terem42
Copy link

terem42 commented Oct 13, 2021

Tested AWS with logical cloning of PR 188 and saving dblab state to file if container is restarted. It works, but for some reason logicalDump/Restore jobs are started too.
As a result, every time after dle restart, a new snapshot is created, which is unacceptable. Possible fix should add a setting to skip these jobs start, if clones for this snapshot already exist.

@terem42 terem42 changed the title after application of PR application of PR 188, jobs always starting after DLE restart Oct 13, 2021
@terem42 terem42 changed the title application of PR 188, jobs always starting after DLE restart after application of PR 188, jobs always starting after DLE restart Oct 13, 2021
@terem42 terem42 changed the title after application of PR 188, jobs always starting after DLE restart after application of MR 188, jobs always starting after DLE restart Oct 13, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant