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.

Sign up for GitHub

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

Jump to bottom

Update Keepalive Configuration in Bigtable Clients #8172

Closed
quartzmo opened this issue Nov 27, 2020 · 0 comments · Fixed by #8173
Closed

Update Keepalive Configuration in Bigtable Clients #8172

quartzmo opened this issue Nov 27, 2020 · 0 comments · Fixed by #8173
Assignees
@quartzmo
Labels
api: bigtable Issues related to the Bigtable API. type: cleanup An internal cleanup or hygiene concern.

Comments

@quartzmo
Copy link
Member

Update the Keepalive Configuration in Bigtable Clients as follows:

Channel argument recommended value
GRPC_ARG_KEEPALIVE_TIME_MS 30s
GRPC_ARG_KEEPALIVE_TIMEOUT_MS 10s

Reference Implementations

Java Hbase Client: googleapis/java-bigtable-hbase#2682
PHP Client: googleapis/google-cloud-php#3565
Java Veneer Client: googleapis/java-bigtable#528
quartzmo added a commit to quartzmo/google-cloud-ruby that referenced this issue Nov 27, 2020
@quartzmo
fix(bigtable-admin-v2): Update keepalive configuration
1060529 
refs: googleapis#8172
quartzmo added a commit to quartzmo/google-cloud-ruby that referenced this issue Nov 27, 2020
@quartzmo
fix(bigtable-v2): Update keepalive configuration
e4672c2 
closes: googleapis#8172
This was referenced Nov 27, 2020
Merged
Closed
@yoshi-automation yoshi-automation added the triage me I really want to be triaged. label Nov 28, 2020
@quartzmo quartzmo added api: bigtable Issues related to the Bigtable API. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. labels Nov 30, 2020
@quartzmo quartzmo self-assigned this Nov 30, 2020
@quartzmo quartzmo added type: cleanup An internal cleanup or hygiene concern. and removed type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. labels Nov 30, 2020
@yoshi-automation yoshi-automation removed the triage me I really want to be triaged. label Nov 30, 2020
quartzmo added a commit that referenced this issue Jan 11, 2021
@quartzmo
fix(bigtable-v2): Update keepalive configuration
e18e527 
closes: #8172
pr: #8173
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@quartzmo quartzmo

Labels
api: bigtable Issues related to the Bigtable API. type: cleanup An internal cleanup or hygiene concern.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix(bigtable-v2): Update keepalive configuration quartzmo/google-cloud-ruby
2 participants
@quartzmo @yoshi-automation