Paweł Pierścionek
Paweł Pierścionek
Hi there - I am experimenting with different HW configs - like moving indexes or account tables to PMEM TABLESPACE . If You have any synthetic workloads please share -...
@robdmoore To confirm this is an issue with follower getting stuck on random relays please try setting this in conduit for a source of blocks: `netaddr: "http://mainnet-api.algonode.cloud"` or for testnet:...
In Coolify v4 you can enable access logging by: - adding a log drain - adding this to proxy config on each server and restarting proxy (does not work on...
I just do fast catchup from a matching catchup from this list https://algorand-catchpoints.s3.us-east-2.amazonaws.com/consolidated/mainnet_catchpoints.txt So downtime is only 40 minutes.
Define crashing. Is the follower really crashing or just failing to deliver the new round in time and indexer just shows a timeout and resumes in a while ? It...
OK. Try this setting in node's config.json: `"CatchupParallelBlocks": 32` or using command line tool: `algocfg set -p CatchupParallelBlocks -v 32` What happens is that Follower sources the blocks from random...
Soon I will be hacking in request coalescing into algod and indexer-api . This is needed in more places.
Nodely will have a PR with this soon. The implementation is live on FNet. playground: https://nodely.io/swagger/index.html?url=/swagger/api/fnet/indexer.oas3.yml#/search/searchForBlocks More here: https://github.com/AlgoNode/indexer-api-cdb/issues/9
Do you think there are use cases where full_header would be too much and some dApp would benefit from smaller response ? What would be the bare bones fields (except...