-
Notifications
You must be signed in to change notification settings - Fork 4k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
BUG#27135742 CLONE CREATED IBDATA1 IS OF A DIFFERENT SIZE
BUG#27245214 LATCHDEBUG::CHECK_ORDER Problem : --------- 1. When file is extended in page copy stage we are always extending the first node/file for the tablespace. For multi-node system tablespace this results in extending the first file more than configured length. 2. For persisting dynamic metadata, checkpoint needs to insert data into tables. A recent patch caused this regression, where checkpoint is called before releasing archiver mutex. This triggers the debug mode assert checking mutex order. 3. Issue when clone lsn with block boundary - when Trailer chunk is first block in next redo file - when trailer chunk ends at file and block boundary 4. Non-linux platforms are not using clone_buffer_size Solution : ---------- 1. Evaluate the right size and extend the last file after PAGE COPY 2. Call checkpoint after releasing archiver mutex 3. Avoid overwriting trailer if archived log ends at block boundary 4. Add check if zero-copy is supported and use clone_buffer_size 5. Tests for scenarios 1-4 5A.Test shutdown while clone is in progress 5B.Test coverage for clone with read/write when not using O_DIRECT Reviewed-by: Satya Bodapati <satya.bodapati@oracle.com> RB: 18427
- Loading branch information
Debarun Banerjee
committed
Jan 31, 2018
1 parent
e2cea82
commit 80013ff
Showing
12 changed files
with
207 additions
and
63 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.