Skip to content

Re-enable the saving of InnoDB dynamic metadata during clone #2

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.

Sign up for GitHub

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

Open
laurynas-biveinis wants to merge 1 commit into
base: fb-mysql-8.0.36-wip
Choose a base branch
from
Open

Re-enable the saving of InnoDB dynamic metadata during clone #2

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions storage/innobase/clone/clone0copy.cc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -537,16 +537,16 @@ int Clone_Snapshot::init_redo_copy(Snapshot_State new_state,
binlog_error = synchronize_binlog_gtid(cbk);
}

#else
int binlog_error = 0;
#endif

/* Save all dynamic metadata to DD buffer table and let all future operations
to save data immediately after generation. This makes clone recovery
independent of dynamic metadata stored in redo log and avoids generating
redo log during recovery. */
dict_persist_t::Enable_immediate dyn_metadata_guard(dict_persist);

#else
int binlog_error = 0;
#endif

/* Use it only for local clone. For remote clone, donor session is different
from the sessions created within mtr test case. */
DEBUG_SYNC_C("clone_donor_after_saving_dynamic_metadata");
Expand Down