You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
terem42
changed the title
after application of PR
application of PR 188, jobs always starting after DLE restart
Oct 13, 2021
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
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
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.
The text was updated successfully, but these errors were encountered: