Should expose a way to force the HS to retry pending transactions to the AS (SYN-411)

[matrixbot]

Submitted by @​matthew:matrix.org
See @​mirw:matrix.mirw.cw-ngv.com's feedback from tadhack June 14

(Imported from https://matrix.org/jira/browse/SYN-411)

[matrixbot]

Jira watchers: @kegsay

[matrixbot]

The AS went down, so the HS would've been backing off. Matthew's instinct here was right : "i suspect it's doing exponential backoff on retrying to the AS".

I'm open to suggestions on how to improve this, probably providing a way to kick the timers to retry immediately. How the kick is exposed (http poke, shell command, etc) and whether this is spec worthy would make for an interesting discussion.

-- @kegsay

[matrixbot]

For record keeping, the transcript from #matrix:

I've just hit an issue where synapse doesn't seem to be notifying my application service of events. I see the events going from my browser to synapse... but then not on to the application service. homeserver.log doesn't show synapse attempting to send notifications (and they don't show up in tcpdump either). This was working earlier, but then there was a period where my application service was down, and I wonder whether synapse has "blacklisted" it?

-- @kegsay

[H-Shay]

Closed in favor of #14240