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

[fix][txn] Implement compatibility for transaction buffer segmented snapshot feature upgrade #20235

Merged
merged 7 commits into from
May 16, 2023
Merged

[fix][txn] Implement compatibility for transaction buffer segmented snapshot feature upgrade #20235

merged 7 commits into from
May 16, 2023

Conversation

liangyepianzhou
Copy link
Contributor

master #16913

Motivation:

The transaction buffer segmented snapshot feature aims to improve the transaction buffer's performance by segmenting the snapshot and managing it more efficiently. However, for existing topics that were created before this feature was introduced, we need to ensure a seamless transition and compatibility when enabling the segmented snapshot feature.

Modifications:

  1. Updated the recoverFromSnapshot() method to read from another topic if the persistentSnapshotIndexes is null. This ensures that the appropriate snapshot data is fetched during the recovery process when upgrading to the segmented snapshot feature.
  2. Created a new test testSnapshotProcessorUpdate() that verifies the compatibility of the transaction

Verifying this change

  • Make sure that the change passes the CI checks.

(Please pick either of the following options)

This change is a trivial rework / code cleanup without any test coverage.

(or)

This change is already covered by existing tests, such as (please describe tests).

(or)

This change added tests and can be verified as follows:

(example:)

  • Added integration tests for end-to-end deployment with large payloads (10MB)
  • Extended integration test for recovery after broker failure

Does this pull request potentially affect one of the following parts:

If the box was checked, please highlight the changes

  • Dependencies (add or upgrade a dependency)
  • The public API
  • The schema
  • The default values of configurations
  • The threading model
  • The binary protocol
  • The REST endpoints
  • The admin CLI options
  • The metrics
  • Anything that affects deployment

Documentation

  • doc
  • doc-required
  • doc-not-needed
  • doc-complete

Matching PR in forked repository

PR in forked repository:

…napshot feature upgrade

## Motivation:
The transaction buffer segmented snapshot feature aims to improve the transaction buffer's performance by segmenting the snapshot and managing it more efficiently. However, for existing topics that were created before this feature was introduced, we need to ensure a seamless transition and compatibility when enabling the segmented snapshot feature.

## Modifications:
1. Updated the `recoverFromSnapshot()` method to read from another topic if the `persistentSnapshotIndexes` is null. This ensures that the appropriate snapshot data is fetched during the recovery process when upgrading to the segmented snapshot feature.
2. Created a new test `testSnapshotProcessorUpdate()` that verifies the compatibility of the transaction
@github-actions github-actions bot added the doc-not-needed Your PR changes do not impact docs label May 5, 2023
@liangyepianzhou liangyepianzhou self-assigned this May 5, 2023
@Technoboy- Technoboy- added this to the 3.1.0 milestone May 15, 2023
@congbobo184 congbobo184 merged commit 8b929e6 into apache:master May 16, 2023
congbobo184 pushed a commit that referenced this pull request May 18, 2023
…napshot feature upgrade (#20235)

master #16913
## Motivation:
The transaction buffer segmented snapshot feature aims to improve the transaction buffer's performance by segmenting the snapshot and managing it more efficiently. However, for existing topics that were created before this feature was introduced, we need to ensure a seamless transition and compatibility when enabling the segmented snapshot feature.

## Modifications:
1. Updated the `recoverFromSnapshot()` method to read from another topic if the `persistentSnapshotIndexes` is null. This ensures that the appropriate snapshot data is fetched during the recovery process when upgrading to the segmented snapshot feature.
2. Created a new test `testSnapshotProcessorUpdate()` that verifies the compatibility of the transaction

### Verifying this change

- [ ] Make sure that the change passes the CI checks.

*(Please pick either of the following options)*

This change is a trivial rework / code cleanup without any test coverage.

*(or)*

This change is already covered by existing tests, such as *(please describe tests)*.

*(or)*

This change added tests and can be verified as follows:

*(example:)*
  - *Added integration tests for end-to-end deployment with large payloads (10MB)*
  - *Extended integration test for recovery after broker failure*

(cherry picked from commit 8b929e6)
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.

4 participants