-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Document BigQuery RPC settings #24638
base: master
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change | ||||
---|---|---|---|---|---|---|
|
@@ -177,6 +177,59 @@ a few caveats: | |||||
- Enable using Apache Arrow serialization when reading data from BigQuery. | ||||||
Please read this [section](bigquery-arrow-serialization-support) before using this feature. | ||||||
- `true` | ||||||
* - `bigquery.channel-pool.initial-size` | ||||||
- The initial size of the connection pool, also known as a channel pool, | ||||||
used for gRPC communication. | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. do we explain gRPC and RPC somewhere earlier in the doc? If not .. we might want to .. or at least link to some external doc |
||||||
- `1` | ||||||
* - `bigquery.channel-pool.min-size` | ||||||
- The absolute minimum size of the connection pool, also known as a channel | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Also ... size in what .. maybe better The minimum number of connections in the connection pool, ... |
||||||
pool, used for gRPC communication. | ||||||
- `1` | ||||||
* - `bigquery.channel-pool.max-size` | ||||||
- The absolute maximum size of the connection pool, also known as a channel | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. See above also |
||||||
pool, used for gRPC communication. | ||||||
- `1` | ||||||
* - `bigquery.channel-pool.min-rpc-per-channel` | ||||||
- Threshold to start scaling down the channel pool. | ||||||
When the average of the maximum number of outstanding RPCs in a single | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Can we simplify to
Suggested change
|
||||||
minute drop below this threshold, channels will be removed from the pool. | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||
- `0` | ||||||
* - `bigquery.channel-pool.max-rpc-per-channel` | ||||||
- Threshold to start scaling up the channel pool. | ||||||
When the average of the maximum number of outstanding RPCs in a single | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Same as preceding |
||||||
minute surpass this threshold, channels will be added to the pool. | ||||||
- `2147483647` | ||||||
* - `bigquery.rpc-retries` | ||||||
- The maximum number of retry attempts to perform for the RPC calls. | ||||||
If this value is set to `0`, the logic will instead use the | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||
`bigquery.rpc-timeout` configuration value to determine retries. | ||||||
In the event that both the `bigquery.rpc-retries` and | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. too many "both" |
||||||
`bigquery.rpc-timeout` values are both `0`, the logic will not retry. | ||||||
If this value is positive, and the number of attempts exceeds | ||||||
`bigquery.rpc-retries` limit, the logic will give up retrying even if | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. same as preceding |
||||||
the total retry time is still lower than `bigquery.rpc-timeout`. | ||||||
- `0` | ||||||
* - `bigquery.rpc-timeout` | ||||||
- Timeout [duration](prop-type-duration) on when the retries for the | ||||||
RPC call should be given up completely. The higher the timeout, the | ||||||
more retries can be attempted. If this value is `0s`, then | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. then the value from |
||||||
the logic will instead use `bigquery.rpc-retries` to determine retries. | ||||||
In the event that `bigquery.rpc-retries` and `bigquery.rpc-timeout` | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Retry is deactivated when both .. and .. are |
||||||
values are both `0`, the logic will not retry. | ||||||
If this value is positive, and the retry duration has reached the timeout | ||||||
value, the logic will give up retrying even the number of attempts is | ||||||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||
lower than the `bigquery.rpc-retries` value. | ||||||
- `0s` | ||||||
* - `bigquery.rpc-retry-delay` | ||||||
- The delay [duration](prop-type-duration) before the first retry attempt | ||||||
for RPC calls. | ||||||
- `0s` | ||||||
* - `bigquery.rpc-retry-delay-multiplier` | ||||||
- Controls the change in delay before the next retry. | ||||||
The retry delay of the previous call is multiplied by the | ||||||
`bigquery.rpc-retry-delay-multiplier` to calculate the retry delay | ||||||
for the next RPC call. | ||||||
- `1.0` | ||||||
* - `bigquery.rpc-proxy.enabled` | ||||||
- Use a proxy for communication with BigQuery. | ||||||
- `false` | ||||||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you remove the "Please" here .. in a separate commit if you want