Closed rogeralsing closed 9 months ago
It would be fine to work on the priority, but as per the present proto.actor code also, we can configure the gossip (system level messages) intervals and timeouts. Also another disadvantage is if we put a long gossip interval, other cluster members would be in an inconsistent state regarding the information of the grains/actors. How can we tackle this?
Done
Make it possible to give some messages priority for the Remote layer. E.g. Gossip messages.
This can probably be solved with a priority queue, or an approach similar to system vs user messages for the mailbox. The idea is to make gossip timeouts less frequent when a system is under heavy load