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][client] Fix ReaderBuilder doest not give illegalArgument on connection failure retry #22639

Merged
merged 2 commits into from
May 10, 2024

Conversation

rdhabalia
Copy link
Contributor

@rdhabalia rdhabalia commented May 2, 2024

Fixes #22638

Motivation

Currently when Reader Builder is used to create Reader with startMessageFromRollbackDuration and if it fails due to connection issue and application retries to create a new Reader again then it throws IllegalArgument Exception even though Reader doesn't have any incorrect argument and that confuses the users.

Modifications

Application should be able to retry and able to recreate Reader using the ReaderBuilder if it fails due to connection issue.

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:

@rdhabalia rdhabalia added area/client doc-not-needed Your PR changes do not impact docs ready-to-test labels May 2, 2024
@rdhabalia rdhabalia added this to the 3.3.0 milestone May 2, 2024
@rdhabalia rdhabalia self-assigned this May 2, 2024
@coderzc coderzc modified the milestones: 3.3.0, 3.4.0 May 8, 2024
Copy link
Member

@lhotari lhotari left a comment

Choose a reason for hiding this comment

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

LGTM

@lhotari
Copy link
Member

lhotari commented May 10, 2024

the check that needed to be revisited was added in #6392

@lhotari lhotari merged commit b56f238 into apache:master May 10, 2024
50 of 51 checks passed
lhotari pushed a commit that referenced this pull request May 14, 2024
lhotari pushed a commit that referenced this pull request May 14, 2024
nikhil-ctds pushed a commit to datastax/pulsar that referenced this pull request May 15, 2024
…nection failure retry (apache#22639)

(cherry picked from commit b56f238)
(cherry picked from commit 8b2d5e9)
srinath-ctds pushed a commit to datastax/pulsar that referenced this pull request May 16, 2024
…nection failure retry (apache#22639)

(cherry picked from commit b56f238)
(cherry picked from commit 8b2d5e9)
lhotari pushed a commit that referenced this pull request Oct 30, 2024
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.

[Bug] ReaderBuilder changes config state during reader creation failure due to server connection failure
4 participants