iotaledger / iota / 28910991576

push

github

fix(iota-kvstore): use latest version of iota-bigtable crate (#12014)

# Description of change

This PR bumps the `iota-bigtable` dependency to the latest revision,
which adds handling for the transient connection errors that arise when
Google BigTable recycles long-lived gRPC connections.

Previously the client had no retry, so requests in flight on a recycled
connection failed and were surfaced as dropped queries to callers. The
updated `iota-bigtable` retries these transient errors with exponential
backoff and adds a small connection pool to reduce the blast radius of a
single reset.
  
More information is available in the corresponding PR:
https://github.com/iotaledger/iota-bigtable/pull/13

> [!NOTE]
> For now we pin the commit hash, once the `iota-bigtable` PR is merged,
a new tag will be created and used in place of the commit hash.

## Links to any relevant issues

fixes #11978 

## How the change has been tested

- [x] Basic tests (linting, compilation, formatting, unit/integration
tests)
- [ ] Patch-specific tests (correctness, functionality coverage)

- Ran locally on mainnet the iota-rest-kv with updated bigtable,
ensuring the added connection pool didn't cause any unwanted behavior.
- Checked that backoff was triggered correctly.
- Was not able to receive the errors which in first place started this
issue since BigTable connection reset can happen randomly, this isn't
conclusive proof.


### Infrastructure QA (only required for crates that are maintained by
@iotaledger/infrastructure)

> [!NOTE]
> This patch does not affect the normal ingestion operation of the
iota-indexer, thus no further tests were conducted.

0 of 4 new or added lines in 3 files covered. (0.0%)

161000 of 236626 relevant lines covered (68.04%)

462244.91 hits per line