Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Latency spikes at every hour due to connection refreshes

See original GitHub issue

Context: We use on-premise datacenters to connect to Bigtable, with a connection count of 180 (default CPU multiplier), currently on "com.google.cloud.bigtable" % "bigtable-hbase-1.2" % "0.9.6.2", upgrading to latest soon ("bigtable-hbase-1.x" % "1.0.0-pre1")

At every hour, we see a big spike in latency, and we believe there’s some kind of connection refresh that is happening

Can the client do this in the background so it doesn’t impact request timings?

Issue Analytics

State:
Created 6 years ago
Comments:6 (1 by maintainers)

Top GitHub Comments

1reaction

igorbernstein2commented, Mar 9, 2020

We implemented a solution for this in https://github.com/googleapis/java-bigtable/pull/115. We are currently in the process of migrating the hbase adapter to use java-bigtable instead of bigtable-client-core. So it will inherit this feature

0reactions

liufuyangcommented, Mar 13, 2020

@igorbernstein2 Do you know for sure that this setting can solve this hourly issue? Or it only can reduce it in some degree? We tried to use it and it seems not really helping and we still see hourly latency peaks? 🤔 (Perhaps I should ping you at other issue page, as we are not really using hbase, we basically use java-bigtable and we have a java backend server that connections onto bigtable 😃)