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 - New add queue should not previously sent message. #830

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

casuallc
Copy link
Contributor

Motivation

New add queue can only receive message that send after queue add to exchange.

Modifications

Verifying this change

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): (no)
  • The public API: (no)
  • The schema: (no)
  • The default values of configurations: (no)
  • The wire protocol: (no)
  • The rest endpoints: (no)
  • The admin cli options: (no)
  • Anything that affects deployment: (no)

Documentation

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

Need to update docs?

  • no-need-doc

@github-actions github-actions bot added the no-need-doc This pr does not need any document label Feb 24, 2023
@@ -297,7 +297,7 @@ private CompletableFuture<ManagedCursor> createCursorIfNotExists(String name) {
if (log.isDebugEnabled()) {
log.debug("Create cursor {} for topic {}", name, persistentTopic.getName());
}
ledger.asyncOpenCursor(name, CommandSubscribe.InitialPosition.Earliest,
Copy link
Collaborator

Choose a reason for hiding this comment

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

Sorry for the late response, if the queue is added the first time, we can set the position to Latest , if the queue is added due to recovery, we need to set the position to Earliest, or messages which are not routed completely, not routing messages may be lost.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

The cursor would be add when queue added, and delete after queue deleted or unbind.
I'm not sure why the cursor created when queue recovery?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
no-need-doc This pr does not need any document
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants