blockworks-foundation
/
solana
mirror of https://github.com/blockworks-foundation/solana.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
solana/storage-bigtable
History
steviez b6d8174aba
bigtable: Adjust logging and condense counters (#31661) 
* bigtable: Demote log lines for entering functions to trace
* bigtable: Condense counters into single datapoint

Counters (inc_new_counter_*) incur extra overhead in that each update
can result in an item being sent over crossbeam channel to MetricsAgent.

So, accumulate the counter locally and submit as datapoint later.
 		2023-05-15 21:48:00 -05:00
..
build-proto chore: workspace inheritance (#29893) 2023-02-23 22:01:54 +08:00
proto Bump tonic from 0.8.2 to 0.8.3 (#29697) 2023-01-31 15:44:39 -07:00
src bigtable: Adjust logging and condense counters (#31661) 2023-05-15 21:48:00 -05:00
Cargo.toml chore: workspace inheritance (#29893) 2023-02-23 22:01:54 +08:00
README.md bigtable: allow forward proxy in gRPC connection (#25918) 2022-06-23 10:51:31 -06:00
init-bigtable.sh
…

README.md

BigTable Setup

Development Environment

The Cloud BigTable emulator can be used during development/test. See https://cloud.google.com/bigtable/docs/emulator for general setup information.

Process:

  1. Run gcloud beta emulators bigtable start in the background
  2. Run $(gcloud beta emulators bigtable env-init) to establish the BIGTABLE_EMULATOR_HOST environment variable
  3. Run ./init-bigtable.sh to configure the emulator
  4. Develop/test

Production Environment

Export a standard GOOGLE_APPLICATION_CREDENTIALS environment variable to your service account credentials. The project should contain a BigTable instance called solana-ledger that has been initialized by running the ./init-bigtable.sh script.

Depending on what operation mode is required, either the https://www.googleapis.com/auth/bigtable.data or https://www.googleapis.com/auth/bigtable.data.readonly OAuth scope will be requested using the provided credentials.

Forward proxy

Export BIGTABLE_PROXY environment variable for the forward proxy as you would for HTTP_PROXY. This will establish a tunnel through the forward proxy for gRPC traffic (the tunneled traffic will still use TLS as normal).