mirror/erigon-pulse
1
0
Fork 0
mirror of https://gitlab.com/pulsechaincom/erigon-pulse.git synced 2024-12-22 03:30:37 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Docs read db (#2103)

Browse Source 
* docs for

* allow anonymous viewers of grafana board
This commit is contained in:
Alex Sharov 2021-06-05 21:10:01 +07:00 committed by GitHub
parent 95d686f24a
commit 6fc8905ce5
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 30 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
cmd/prometheus/grafana.ini
View File

@ -312,13 +312,13 @@ level = warn
#################################### Anonymous Auth ######################
[auth.anonymous]
# enable anonymous access
;enabled = false
enabled = true
# specify organization name that should be used for unauthenticated users
;org_name = Main Org.
# specify role for unauthenticated users
;org_role = Viewer
org_role = Viewer
# mask the Grafana version number for unauthenticated users
;hide_version = false

4
cmd/rpcdaemon/README.md
View File

@ -381,6 +381,10 @@ Increase it - if your 'hot data' is small or have much RAM or see "request timeo
Reduce `--private.api.ratelimit`
### Read DB directly without Json-RPC/Graphql
[./docs/programmers_guide/read_db.md](./docs/programmers_guide/read_db.md)
## For Developers
### Code generation

24
docs/programmers_guide/read_db.md Normal file
View File

@ -0,0 +1,24 @@
# How to read DB directly - not by Json-RPC/Graphql:
There are 2 options exist:
1. call --private.api.addr there is grpc interface with low-level data access methods - can read any data in any order,
etc... Interface is here: https://github.com/ledgerwatch/interfaces/blob/master/remote/kv.proto
Go/C++/Rust libs already exist. Names of buckets and their format you can find in `bucket.go` You can do such calls
by network.
2. Read Erigon's db while Erigon is running - it's also ok - just need be careful - do not run too long read
transactions (long read transactions do block free space in DB). Then your app will share with Erigon same OS-level
PageCache where hot part of db stored. It may be great - if you read hot data (for example do incremental update of
graph node) - then your reads will be super fast and almost never touch disk. But if you wanna read cold data - then
your app will load cold data to PageCache and maybe evict some Erigon's hot data. Probably it will not be very
dangerous - because your reads will happen once while Erigon will touch hot data often and OS's built-in LRU will
understand which data is more Hot and keep it in RAM.
this 2 options ^ are exactly how RPCDaemon works with flags `--private.api.addr` and `--datadir`. One by using grpc
interface, another by opening Erigon's db in read-only mode while Erigon running. But both this options are
using `RoKV` (stands for read-only) `kv_abstract.go` interface. Option 1 using `kv_remote.go` to implement `RoKV`,
option 2 using - `kv_mdbx.go`
Erigon using MDBX database. But any articles in internet about LMDB are also valid for MDBX.
We have Go, Rust and C++ implementations of `RoKV` interface.