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

refactor: use separate configuration for exchange connection pool for batch and streaming #17768

Merged
merged 2 commits into from
Jul 23, 2024

Conversation

BugenZhao
Copy link
Member

@BugenZhao BugenZhao commented Jul 22, 2024

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.

What's changed and what's your intention?

See comment from @kwannoel in #17755 (review) for the background.

Follow-up of #17755. Introduce two configuration entries of batch.developer.exchange_connection_pool_size and streaming.developer.exchange_connection_pool_size, which override the server.connection_pool_size if set.

The default values of them are set to None and Some(1) correspondingly to be compatible with the behavior before this and the previous PR.

Checklist

  • I have written necessary rustdoc comments
  • I have added necessary unit tests and integration tests
  • All checks passed in ./risedev check (or alias, ./risedev c)

Documentation

  • My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note

Introduce two configuration entries of batch.developer.exchange_connection_pool_size and streaming.developer.exchange_connection_pool_size. See documentation for more details.

Copy link
Member Author

BugenZhao commented Jul 22, 2024

Copy link
Contributor

@kwannoel kwannoel left a comment

Choose a reason for hiding this comment

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

LGTM, thanks!

@BugenZhao BugenZhao force-pushed the bz/client-pool-separate-config branch from 0991157 to f5ae55d Compare July 23, 2024 03:41
@BugenZhao BugenZhao added the user-facing-changes Contains changes that are visible to users label Jul 23, 2024
@BugenZhao BugenZhao marked this pull request as ready for review July 23, 2024 04:05
@BugenZhao BugenZhao requested a review from chenzl25 July 23, 2024 04:06
Base automatically changed from bz/stream-client-pool to main July 23, 2024 04:42
@graphite-app graphite-app bot requested a review from a team July 23, 2024 04:42
@BugenZhao BugenZhao force-pushed the bz/client-pool-separate-config branch from f5ae55d to 0be5d74 Compare July 23, 2024 05:25
@BugenZhao BugenZhao added this pull request to the merge queue Jul 23, 2024
Merged via the queue into main with commit 2e53024 Jul 23, 2024
30 of 31 checks passed
@BugenZhao BugenZhao deleted the bz/client-pool-separate-config branch July 23, 2024 07:33
@kwannoel kwannoel added the need-cherry-pick-release-1.10 Open a cherry-pick PR to branch release-1.10 after the current PR is merged label Jul 24, 2024
kwannoel pushed a commit that referenced this pull request Jul 25, 2024
kwannoel pushed a commit that referenced this pull request Jul 25, 2024
github-merge-queue bot pushed a commit that referenced this pull request Jul 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
need-cherry-pick-release-1.10 Open a cherry-pick PR to branch release-1.10 after the current PR is merged type/refactor user-facing-changes Contains changes that are visible to users
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants