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][Transaction] Fix transaction pendingAckStore asyncMarkDelete #14974

Merged
merged 5 commits into from
Apr 2, 2022
Merged

[Fix][Transaction] Fix transaction pendingAckStore asyncMarkDelete #14974

merged 5 commits into from
Apr 2, 2022

Conversation

liangyepianzhou
Copy link
Contributor

Motivation

When we only use transaction to ack message, a message per transaction,
cursor.asyncMarkDelete will never be executed, because firstPosition and
deletePosition both are init as metadataPositions.firstEntry().getKey();
And if only the firstkey need to delete, deletePosition also get metadataPositions.firstKey(); irstPosition == deletePosition, never call cursor.asyncMarkDelete

Modification

init firstPosition and deletePosition as PositionImpl.EARLIEST

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 yes was chosen, please highlight the changes

  • Dependencies (does it add or upgrade a dependency): (yes / no)
  • The public API: (yes / no)
  • The schema: (yes / no / don't know)
  • The default values of configurations: (yes / no)
  • The wire protocol: (yes / no)
  • The rest endpoints: (yes / no)
  • The admin cli options: (yes / no)
  • Anything that affects deployment: (yes / no / don't know)

Documentation

Check the box below or label this PR directly (if you have committer privilege).

Need to update docs?

  • doc-required

    (If you need help on updating docs, create a doc issue)

  • no-need-doc

    (Please explain why)

  • doc

    (If this PR contains doc changes)

### Motivation
When we only use transaction to ack message, a message per transaction,
`cursor.asyncMarkDelete` will never be executed, because firstPosition and
 deletePosition both are init as metadataPositions.firstEntry().getKey();
 And if only the firstkey need to delete,  deletePosition also get metadataPositions.firstKey(); irstPosition == deletePosition, never call `cursor.asyncMarkDelete`
### Modification
init firstPosition and deletePosition as PositionImpl.EARLIEST
@github-actions github-actions bot added the doc-not-needed Your PR changes do not impact docs label Mar 31, 2022
@congbobo184 congbobo184 added release/2.9.3 release/2.10.1 area/transaction type/bug The PR fixed a bug or issue reported a bug labels Apr 1, 2022
@congbobo184 congbobo184 added this to the 2.11.0 milestone Apr 1, 2022
@liangyepianzhou
Copy link
Contributor Author

/pulsarbot run-failure-checks

@liangyepianzhou
Copy link
Contributor Author

/pulsarbot run-failure-checks

@congbobo184 congbobo184 merged commit 8a6ecd7 into apache:master Apr 2, 2022
congbobo184 pushed a commit that referenced this pull request Apr 2, 2022
…14974)

### Motivation
When we only use transaction to ack message, a message per transaction,
`cursor.asyncMarkDelete` will never be executed, because firstPosition and
 deletePosition both are init as metadataPositions.firstEntry().getKey();
 And if only the firstkey need to delete,  deletePosition also get metadataPositions.firstKey(); irstPosition == deletePosition, never call `cursor.asyncMarkDelete`
### Modification
init firstPosition and deletePosition as PositionImpl.EARLIEST

(cherry picked from commit 8a6ecd7)
@codelipenghui codelipenghui added the cherry-picked/branch-2.9 Archived: 2.9 is end of life label Apr 2, 2022
codelipenghui pushed a commit that referenced this pull request Apr 19, 2022
…14974)

### Motivation
When we only use transaction to ack message, a message per transaction,
`cursor.asyncMarkDelete` will never be executed, because firstPosition and
 deletePosition both are init as metadataPositions.firstEntry().getKey();
 And if only the firstkey need to delete,  deletePosition also get metadataPositions.firstKey(); irstPosition == deletePosition, never call `cursor.asyncMarkDelete`
### Modification
init firstPosition and deletePosition as PositionImpl.EARLIEST

(cherry picked from commit 8a6ecd7)
Nicklee007 pushed a commit to Nicklee007/pulsar that referenced this pull request Apr 20, 2022
…pache#14974)

### Motivation
When we only use transaction to ack message, a message per transaction,
`cursor.asyncMarkDelete` will never be executed, because firstPosition and
 deletePosition both are init as metadataPositions.firstEntry().getKey();
 And if only the firstkey need to delete,  deletePosition also get metadataPositions.firstKey(); irstPosition == deletePosition, never call `cursor.asyncMarkDelete`
### Modification
init firstPosition and deletePosition as PositionImpl.EARLIEST
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/transaction cherry-picked/branch-2.9 Archived: 2.9 is end of life cherry-picked/branch-2.10 doc-not-needed Your PR changes do not impact docs release/2.9.3 release/2.10.1 type/bug The PR fixed a bug or issue reported a bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants