Skip to content

feat(Spanner): modify default maxConcurrentStreamsLowWatermark value … - #8933

Merged
alkatrivedi merged 3 commits into
mainfrom
dcp-watermark
Jul 23, 2026
Merged

feat(Spanner): modify default maxConcurrentStreamsLowWatermark value …#8933
alkatrivedi merged 3 commits into
mainfrom
dcp-watermark

Conversation

@alkatrivedi

Copy link
Copy Markdown
Contributor

This PR modifies the default value of maxConcurrentStreamsLowWatermark from 100 to 25. This is to make the value consistent with Java client. As part of this change one channel can have at max 25 concurrent request at time, once the threshold will reach the channels will get scale up.

@alkatrivedi
alkatrivedi requested a review from a team as a code owner July 22, 2026 10:42
@product-auto-label product-auto-label Bot added the api: spanner Issues related to the Spanner API. label Jul 22, 2026

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Code Review

This pull request updates the maxConcurrentStreamsLowWatermark configuration value from 100 to 25 in spanner_grpc_config.json. There are no review comments, and I have no additional feedback to provide.

"gcp-metadata": "^7.0.1",
"@sinonjs/fake-timers": "15.2.1"
"@sinonjs/fake-timers": "15.2.1",
"@eslint-community/eslint-utils": "<4.10.0"

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

need this change since, the package @eslint-community/eslint-utils (which is pulled in automatically by eslint via gts@6.0.2) recently released version 4.10.0.
In version 4.10.0, they updated their engines field in package.json to require Node.js ^20.19.0 || ^22.13.0 || >=24, effectively dropping support for Node 18.
Our GitHub Actions presubmit job is running Node v18.20.8. Because pnpm install is being executed with the --engine-strict flag, pnpm strictly enforces these Node engine requirements and immediately fails the installation.

@alkatrivedi
alkatrivedi merged commit 7d991ec into main Jul 23, 2026
35 checks passed
@alkatrivedi
alkatrivedi deleted the dcp-watermark branch July 23, 2026 05:43
@alkatrivedi alkatrivedi added the release-please:force-run To run release-please label Jul 23, 2026
@release-please release-please Bot removed the release-please:force-run To run release-please label Jul 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

api: spanner Issues related to the Spanner API.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants