xmtpd icon indicating copy to clipboard operation
xmtpd copied to clipboard

Failover when an originator becomes unresponsive, and return to originator once responsive

Open mkysel opened this issue 1 year ago • 4 comments

mkysel avatar Oct 28 '24 14:10 mkysel

This might already be done. To be investigated.

mkysel avatar Oct 28 '24 14:10 mkysel

We will re-establish a connection in the syncworker if an originator crashes. I have seen this work plenty of times. I don't think that we have any explicit testing for it.

Is there anything else that needs to happen here @richardhuaaa?

mkysel avatar Oct 28 '24 18:10 mkysel

I think there's two more cases we need to handle:

  1. If the originator is in the registry, but for some reason we are unable to connect to it even on retry, we should pull that originator's payloads from other nodes on the network (perhaps multiple).

  2. if the originator was recently removed from the registry (e.g. within 1 day), or they have been removed long ago but we are a brand new node that has no history, we should pull that originator's payloads from other nodes on the network (perhaps multiple)

The XIP could def do a better job of going through these

richardhuaaa avatar Oct 28 '24 23:10 richardhuaaa

Gotcha. Thanks for the details

mkysel avatar Oct 29 '24 16:10 mkysel

Won't do.

mkysel avatar Nov 12 '25 20:11 mkysel