Stuck block lookup on nodes running latest unstable #8104
Description
Description
Please provide a brief description of the issue.
Version
unstable
Present Behaviour
Seeing quite a lot of stuck lookup logs after latest unstable deployment to our sepolia and hoodi nodes:
Sep 22 03:06:54.358 WARN Notify the devs a sync lookup is stuck block_root: 0x7eb2f7a1660008dacb0ea735b9f5cf7210822ae09233a2f10bd6b30b365deff3, lookup: SingleBlockLookup { id: 420, block_request_state: BlockRequestState { state: SingleLookupRequestState { state: AwaitingDownload(block in processing cache), failed_processing: 0, failed_downloading: 0 } }, component_requests: ActiveBlobRequest(BlobRequestState { state: SingleLookupRequestState { state: Processed(no indices to fetch), failed_processing: 0, failed_downloading: 0 } }, 8), peers: 1, block_root: 0x7eb2f7a1660008dacb0ea735b9f5cf7210822ae09233a2f10bd6b30b365deff3, awaiting_parent: None, created: Instant { tv_sec: 2487708, tv_nsec: 655628474 }, span: Span { name: "single_block_lookup", level: Level(Debug), target: "network::sync::block_lookups::single_block_lookup", id: Id(8455515447213686799), module_path: "network::sync::block_lookups::single_block_lookup", line: 95, file: "beacon_node/network/src/sync/block_lookups/single_block_lookup.rs" } }
The most recent stuck lookup fix was #8005, it seemed to improve things looking at metrics at the time but may have introduced some other failure cases.