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

Copy and move index file only when there are changes #434

Conversation

abhinav04sharma
Copy link
Contributor

Summary: When index file is updated, it is first copied to a crash safe index
file, updates are made to the crash safe file and finally the crash safe file is
renamed. During purge, all this should happen only when at least one log is
being removed.

Test Plan: Checked if all existing test cases pass

Summary: When index file is updated, it is first copied to a crash safe index
file, updates are made to the crash safe file and finally the crash safe file is
renamed. During purge, all this should happen only when at least one log is
being removed.

Test Plan: Checked if all existing test cases pass
@facebook-github-bot
Copy link

@abhinav04sharma has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator.

@abhinav04sharma abhinav04sharma deleted the optimize_index_file_update branch November 21, 2016 22:20
abhinav04sharma added a commit to abhinav04sharma/mysql-5.6 that referenced this pull request Dec 6, 2016
Summary:
When index file is updated, it is first copied to a crash safe index
file, updates are made to the crash safe file and finally the crash safe file is
renamed. During purge, all this should happen only when at least one log is
being removed.
Closes facebook#434
Github Author: Abhinav Sharma <abhinavsharma@fb.com>

Github PR Sync: {sync, type="child", parent="github", parentrepo="facebook/mysql-5.6", parentprnum="434", parentprfbid="171820066615445"}

Test Plan:  Checked if all existing test cases pass

Reviewers: herman, santoshb, svcscm

Reviewed By: santoshb, svcscm

Subscribers: svcscm, webscalesql-eng@

Differential Revision: https://phabricator.intern.facebook.com/D4198759

Tasks: 13668299

Signature: t1:4198759:1479408838:1696fa31943f1db04e284baed289e0db33ad5a19
hermanlee pushed a commit that referenced this pull request Jan 31, 2017
Summary:
When index file is updated, it is first copied to a crash safe index
file, updates are made to the crash safe file and finally the crash safe file is
renamed. During purge, all this should happen only when at least one log is
being removed.
Closes #434

Reviewed By: santoshbanda

Differential Revision: D4198759

Pulled By: abhinav04sharma

fbshipit-source-id: 90a1d5c
VitaliyLi pushed a commit to VitaliyLi/mysql-5.6 that referenced this pull request Feb 9, 2017
Summary:
When index file is updated, it is first copied to a crash safe index
file, updates are made to the crash safe file and finally the crash safe file is
renamed. During purge, all this should happen only when at least one log is
being removed.
Closes facebook#434

Reviewed By: santoshbanda

Differential Revision: D4198759

Pulled By: abhinav04sharma

fbshipit-source-id: 90a1d5c
inikep pushed a commit to inikep/mysql-5.6 that referenced this pull request Feb 7, 2019
Jira ticket: https://jira.percona.com/browse/FB8-85

Reference Patch: facebook@4a1823a

Can be squashed with FB8-77 `Changed the behavior of purging logs. Now deleting logs first and then updating the index.`:
https://jira.percona.com/browse/FB8-77
facebook@97ae20b

Summary:
When index file is updated, it is first copied to a crash safe index
file, updates are made to the crash safe file and finally the crash safe file is
renamed. During purge, all this should happen only when at least one log is
being removed.
Closes facebook#434

Originally Reviewed By: santoshbanda

Pulled By: abhinav04sharma

fbshipit-source-id: 90a1d5c
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants