lighthouse/beacon_node/http_api/tests
Paul Hauner 661307dce1 Separate committee subscriptions queue (#3508)
## Issue Addressed

NA

## Proposed Changes

As we've seen on Prater, there seems to be a correlation between these messages

```
WARN Not enough time for a discovery search  subnet_id: ExactSubnet { subnet_id: SubnetId(19), slot: Slot(3742336) }, service: attestation_service
```

... and nodes falling 20-30 slots behind the head for short periods. These nodes are running ~20k Prater validators.

After running some metrics, I can see that the `network_recv` channel is processing ~250k `AttestationSubscribe` messages per minute. It occurred to me that perhaps the `AttestationSubscribe` messages are "washing out" the `SendRequest` and `SendResponse` messages. In this PR I separate the `AttestationSubscribe` and `SyncCommitteeSubscribe` messages into their own queue so the `tokio::select!` in the `NetworkService` can still process the other messages in the `network_recv` channel without necessarily having to clear all the subscription messages first.

~~I've also added filter to the HTTP API to prevent duplicate subscriptions going to the network service.~~

## Additional Info

- Currently being tested on Prater
2022-08-30 05:47:31 +00:00
..
common.rs Separate committee subscriptions queue (#3508) 2022-08-30 05:47:31 +00:00
fork_tests.rs Use async code when interacting with EL (#3244) 2022-07-03 05:36:50 +00:00
interactive_tests.rs Use async code when interacting with EL (#3244) 2022-07-03 05:36:50 +00:00
main.rs Fix chain_id value in config/deposit_contract RPC method (#2659) 2021-10-01 06:32:38 +00:00
tests.rs Separate committee subscriptions queue (#3508) 2022-08-30 05:47:31 +00:00