chore: debug slow relayer startup (#3932)
### Description Opened this PR to debug slow relayer startup, but it actually looks like that's already been fixed by hook indexing. The requirement for fast startup is that the processor sees new messages and then one of the following happens: - (1) if the message is meant for an unknown domain, it drops it ([this log](pull/3946/head6d132b02a3/rust/agents/relayer/src/msg/processor.rs (L269)
)), otherwise - it forwards the message to the submitter, which then: - (2) adds it straight to the confirm queue because it's already been submitted ([here](6d132b02a3/rust/agents/relayer/src/msg/pending_message.rs (L159)
)) - (3) successfully builds metadata ([here](6d132b02a3/rust/agents/relayer/src/msg/op_submitter.rs (L231)
)) - (4) in some cases building metadata fails because the ism doesn't exist The relayer logs either of the four cases (in most cases (2), because we're running a second relayer for now). To be even more confident in fast startup, I ran a single relayer and restarted it. New messages were successfully processed according to one of the four cases above, and the prep queues didn't increase ### Drive-by changes <!-- Are there any minor or drive-by changes also included? --> ### Related issues <!-- - Fixes #[issue number here] --> ### Backward compatibility <!-- Are these changes backward compatible? Are there any infrastructure implications, e.g. changes that would prohibit deploying older commits using this infra tooling? Yes/No --> ### Testing <!-- What kind of testing have these changes undergone? None/Manual/Unit Tests -->
parent
9f19cdf469
commit
5a31e7b5d3
Loading…
Reference in new issue