Re: IGNITE-4302 discovery messages to exchange binary metadata - design proposal

2017-01-13 Thread Sergey Chugunov
Vladimir, Alexey, Let me describe my current vision of the task; please correct me if I'm wrong somewhere. 1. The only class adding and retrieving metadata to/from sys-cache is *CacheObjectBinaryProcessorImpl*. I expect all code managing discovery events flow to be placed here.

Re: IGNITE-4302 discovery messages to exchange binary metadata - design proposal

2017-01-13 Thread Alexey Goncharuk
Vladimir, Given that metadata updates will be initiated with DiscoveryCustomEvent, I see no problems neither with total message ordering (the order will be the same on all nodes and consistent with discovery events) nor with failover - the event is marked with @TcpDiscoveryEnsureDelivery, so the

Re: IGNITE-4302 discovery messages to exchange binary metadata - design proposal

2017-01-13 Thread Vladimir Ozerov
Sergey, In my understanding the only difficult thing here is how to disallow usage of not-yet-confirmed metadata during serialization. As we assume metadata updates to be relatively rare, can we always initiate message send from coordinator node? In this case we will have total order of all

IGNITE-4302 discovery messages to exchange binary metadata - design proposal

2017-01-12 Thread Sergey Chugunov
Hello Ignite devs, I came up with the following design proposal for IGNITE-4302 , which is very similar to described here proposal for IGNITE-4157