Peter Argue
Peter Argue
Closes: #2797 Closes: #2718 This is the first PR in a 2 part change. ## Background Access and Execution nodes run bitswap to sync `ExecutionData` amongst themselves. Bitswap has a...
https://github.com/onflow/flow-go/pull/1895 only implements an integration test for Access Node execution state sync because testnet currently does not support the observer. There is work underway to add support. Once the changes...
## Problem Definition The `ExecutionDataRequester` was added to Access Nodes to participate in the execution data sync protocol. It should also be available on Observers so they can also sync...
## Problem Definition The REST api currently does not collect any metrics, so we lack visibility into key metrics. ## Proposed Solution Add metrics collection to the Access node's REST...
## Problem Definition The observer's gRPC interface has functionality to forward gRPC requests that it cannot server locally to an upstream AN. The code is here: https://github.com/onflow/flow-go/blob/4b6dd69e732991087ba70287f4b6f99dba72cdff/engine/access/apiproxy/access_api_proxy.go There's a section...
## Problem Definition Access nodes use a connection pool for gRPC connections proxied to Execution and Collection nodes. When the pool is full, connections are evict using a least recently...
## Problem Definition When querying an Access Node for data, there's no way to know what the current protocol state is for the AN you are interacting with. This can...
## Problem Definition Currently, the Observer service runs the standard Access API, which forwards requests to staked Collection/Execution Nodes. However, the observer should only interact with its configured staked Access...
Currently, the bitswap network only adds peers to its client/server peer lists that connected after the network has started. This means the network must be started before enabling the libp2p...