`relay-headers-and-messages` command can fail permanently to submit finality headers

[RomarQ]

The relay-headers-and-messages command currently can get stuck with the following log:

Custom("Failed to optimize Kusama GRANDPA jutification for header HeaderId(30409963, 0xff05dbca980ce7c6df208531f16fc7e6b68bad1c373fae2622f3652d95fcb410): Error::TooLowCumulativeWeight")

The only way I have found to solve this problem is to also run relay-headers.

Is this a known issue?

[bkontur]

Hmm, we don't run a single complex relayer for both headers and messages — instead, we run separate relayers for relay-headers, relay-parachains, and relay-messages. In fact, we plan to remove the complex relayer code (relay-headers-and-messages) altogether.

[bkontur]

@serban300 I think I saw some time ago Failed to optimize Kusama GRANDPA jutification somewhere, don't you remember if it could cause issues?

I just found #2394

[RomarQ]

Ok, good to know. Will looking into replacing the complex relayer for both headers and messages. And just use relay-headers, relay-parachains, and relay-messages.

The good thing about the complex relayer was the batching.

[bkontur]

The good thing about the complex relayer was the batching.

Yes, but we want to support free finality for BridgeHubs, so we don't use batching now :)