Decide of the reliability and ordering guarantees of notifications (and implement them) #552
Labels
I3-annoyance
The node behaves within expectations, however this “expected behaviour” itself is at issue.
For context, see the discussion here: paritytech/substrate#6692 (comment)
It is unclear at the moment whether the notifications sent using
NetworkService::write_notification
orNetworkService::notification_sender
provide some guarantee that the notifications will reach their destination and in the same order as they have been sent.99.9% of the time the notifications will indeed reach their destination and in the correct order. The problematic situations are corner cases, most notably the situation where we have multiple connections open, and one of them closes.
cc @romanb
The text was updated successfully, but these errors were encountered: