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

Replace serveral deprecated api usages #13351

Merged

Conversation

shoothzj
Copy link
Member

Modifications

Replace serveral deprecated api usages

Documentation

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

Need to update docs?

  • no-need-doc

trival changes, no need doc

@github-actions github-actions bot added the doc-not-needed Your PR changes do not impact docs label Dec 16, 2021
@shoothzj
Copy link
Member Author

315157973 pushed a commit to 315157973/pulsar that referenced this pull request Dec 16, 2021
…ect (apache#11446)

![image](https://user-images.githubusercontent.com/51213812/126812923-91bb827c-246d-451d-8f25-343bb2c1dca0.png)

befoe this PR precise publish rate limiting wasn't taking effect at all
### Modifications

In order to solve the current problems, there are 2 modifications

1. Using IsDispatchRateLimiting in precise publish rate limiter as well (in order to starve the producer)
2. Checking if there are available permits before resetting the read from the connection again

### Verifying this change

Already covered by current tests.

(cherry picked from commit 00ad07d)
@codelipenghui codelipenghui added this to the 2.10.0 milestone Dec 16, 2021
@merlimat merlimat merged commit c20292c into apache:master Dec 16, 2021
@shoothzj shoothzj deleted the replace-serveral-deprecated-api-usage branch December 16, 2021 23:37
fxbing pushed a commit to fxbing/pulsar that referenced this pull request Dec 19, 2021
shyamvyas5 pushed a commit to pandio-com/pulsar that referenced this pull request Dec 20, 2021
…ect (apache#11446)

![image](https://user-images.githubusercontent.com/51213812/126812923-91bb827c-246d-451d-8f25-343bb2c1dca0.png)

befoe this PR precise publish rate limiting wasn't taking effect at all

In order to solve the current problems, there are 2 modifications

1. Using IsDispatchRateLimiting in precise publish rate limiter as well (in order to starve the producer)
2. Checking if there are available permits before resetting the read from the connection again

Already covered by current tests.

(cherry picked from commit 00ad07d)
pgier pushed a commit to pgier/pulsar that referenced this pull request Jan 6, 2022
…ect (apache#11446)

![image](https://user-images.githubusercontent.com/51213812/126812923-91bb827c-246d-451d-8f25-343bb2c1dca0.png)

befoe this PR precise publish rate limiting wasn't taking effect at all
### Modifications

In order to solve the current problems, there are 2 modifications

1. Using IsDispatchRateLimiting in precise publish rate limiter as well (in order to starve the producer)
2. Checking if there are available permits before resetting the read from the connection again

### Verifying this change

Already covered by current tests.
nicoloboschi pushed a commit to datastax/pulsar that referenced this pull request Jan 26, 2022
…ect (apache#11446)

![image](https://user-images.githubusercontent.com/51213812/126812923-91bb827c-246d-451d-8f25-343bb2c1dca0.png)

befoe this PR precise publish rate limiting wasn't taking effect at all

In order to solve the current problems, there are 2 modifications

1. Using IsDispatchRateLimiting in precise publish rate limiter as well (in order to starve the producer)
2. Checking if there are available permits before resetting the read from the connection again

Already covered by current tests.

(cherry picked from commit 00ad07d)
(cherry picked from commit 06c6adf)
bharanic-dev pushed a commit to bharanic-dev/pulsar that referenced this pull request Mar 18, 2022
…ect (apache#11446)

![image](https://user-images.githubusercontent.com/51213812/126812923-91bb827c-246d-451d-8f25-343bb2c1dca0.png)

befoe this PR precise publish rate limiting wasn't taking effect at all
### Modifications

In order to solve the current problems, there are 2 modifications

1. Using IsDispatchRateLimiting in precise publish rate limiter as well (in order to starve the producer)
2. Checking if there are available permits before resetting the read from the connection again

### Verifying this change

Already covered by current tests.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
doc-not-needed Your PR changes do not impact docs
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants