Datastreamer does not have order guarantees, it guarantees that all data added by addData() calls is stored on closing or flushing data streamer.
Can you please take a look at this - https://apacheignite.readme.io/docs/messaging#section-ordered-messages - and tell me if this works for you. --Yakov 2016-03-16 13:29 GMT+03:00 Andrew <[email protected]>: > Hi, I need your help to improve performance. > > We are using 1 Ignite client node for both receiving messages and flushing > messages into grid-cache, and 4 Ignite server nodes to execute messages of > local partitions of the grid-cache. > For messages from the same sender must be executed on the same server node, > we are using AffinityKey as a key of grid-cache. > As the messages are too massive to put into grid-cache with plain cache > API, > we are using DataStreamer , in spite of the messages have to be executed > strictly ordered per each senders. > Therefore, when we getting messages from grid-cache in server nodes we have > to reorder grid-cache entries and even wait for arrival from DataStreamer. > This is the point which I want to improve. > > How can we distribute messages ordered to each server nodes? > Do we have to change our architecture? then is there any reference? > Or is there any way can execute messages ordered with DataStreamer? > > Sincerely, > Andrew. > > > > -- > View this message in context: > http://apache-ignite-users.70518.x6.nabble.com/How-can-I-achieve-performance-tp3535.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. >
