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

Make compatible between DefaultEntryLogger and DirectEntryLogger #4041

Conversation

horizonzy
Copy link
Member

Descriptions of the changes in this PR:

Fixes #4040

Upgrade guide:
If the user already uses the DirectEntryLogger in production, can not disable DirectEntryLogger directly.

There are two ways:

  1. Upgrade to the version with this PR, and disable DirectEntryLogger. Then restart, and the data won't be lost.
  2. If you don't want to upgrade to the bookie version, you should stop the bookie first, then find the entry log which has the biggest log id. Modify the lastLogId file content using the biggest log id. (Not recommend)

@horizonzy horizonzy closed this Jul 30, 2023
@horizonzy horizonzy reopened this Jul 30, 2023
Copy link
Contributor

@hangc0276 hangc0276 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please add a test to cover this change, thanks.

@horizonzy
Copy link
Member Author

rerun failure checks

Copy link
Contributor

@hangc0276 hangc0276 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice catch!

@zymap zymap merged commit 2e8be78 into apache:master Aug 30, 2023
16 checks passed
zymap pushed a commit that referenced this pull request Aug 30, 2023
Descriptions of the changes in this PR:

Fixes #4040

Upgrade guide:
If the user already uses the DirectEntryLogger in production, can not disable DirectEntryLogger directly.

There are two ways:
1. Upgrade to the version with this PR, and disable DirectEntryLogger. Then restart, and the data won't be lost.
2. If you don't want to upgrade to the bookie version, you should stop the bookie first, then find the entry log which has the biggest log id.  Modify the `lastLogId` file content using the biggest log id. (Not recommend)

---------

Co-authored-by: zymap <zhangyong1025.zy@gmail.com>
(cherry picked from commit 2e8be78)
Ghatage pushed a commit to sijie/bookkeeper that referenced this pull request Jul 12, 2024
…che#4041)

Descriptions of the changes in this PR:

Fixes apache#4040 

Upgrade guide:
If the user already uses the DirectEntryLogger in production, can not disable DirectEntryLogger directly. 

There are two ways:
1. Upgrade to the version with this PR, and disable DirectEntryLogger. Then restart, and the data won't be lost.
2. If you don't want to upgrade to the bookie version, you should stop the bookie first, then find the entry log which has the biggest log id.  Modify the `lastLogId` file content using the biggest log id. (Not recommend)

---------

Co-authored-by: zymap <zhangyong1025.zy@gmail.com>
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.

Data loss problem when DefaultEntryLogger switch to DirectEntryLogger, then switch back to DefaultEntryLogger.
3 participants