Hello! Unfortunately, there's no file attached. Can you provide a link or put reproducer to github?
Thanks. -- Ilya Kasnacheev 2018-05-17 23:02 GMT+03:00 npordash <[email protected]>: > Hi, > > I ran into a situation where I have a client running, all server nodes are > restarted, the client reconnects as expected, but then after creating a new > IgniteStreamer all attempts to send data fail due to a > ClusterTopologyCheckedException. It appears the streamer is attempting to > send data to a server node id that existed prior to the cluster restart. > > However, I'm only seeing this behavior is the stream receiver is set to > anything other than IsolatedUpdater. So setting allowOverride to true or > specifying a custom stream receiver (even those defined in > DataStreamerCacheUpdaters) results in this error. > > A simple reproducer below: > > > > This will fail when the second streamer attempts to close and flush its > internal buffers with a "too many remaps" error which is caused by "Failed > to wait for request completion (node has left): > 02870f63-9cb1-4425-b18f-c5bbf56aa41a" where the node id was for the first > server started in the reproducer. > > -Nick > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
