A few things in consideration:
- We cannot simply whitelist @0.0.0.0:0 in
MESOS-7401 otherwise the protection mechanism is rendered useless.
- Even though some messages are not supposed to have a "return address", it makes sense to always require a non-empty from address for actor to actor communication.
- For non-testing libprocess communication in Mesos it makes sense to assume all messages are sent by libprocess actors.
So for this the easiest fix is probably just give the LearnedMessage a sender: define a simple RequestProcess, in contrast with ReqResProcess, which is used for other replicated log messages.
Of course no attempt has been made in the replicated log to really verify that the learned message is sent by a coordinator so this is simply to make the replicated log compliant with
/cc James Peach Jie Yu