Hi, Yes, that’s the expected behavior. The client is connected to a single server, not both. If the server it’s connected to is killed, the client will reconnect, producing the events in the process. When you kill one of the servers and the client doesn’t get disconnected it’s probably because you’ve killed the wrong one (not the one client is connected to).
Stan From: Bellenger, Dominique Sent: 19 марта 2018 г. 15:32 To: [email protected] Subject: Question about client disco-/reconnect behaviour Hello igniters, I have a question about expected client reconnection behaviour. I have two server nodes and one client node. When everything is connected and one of the servers fails (because it is killed) the client is supposed to 1) Connect to the remaining server transparently, no Disconnect event, no reconnect event 2) Do nothing because it is connected to both servers and switches to the remaining connection silently. No Disconnect event, no Reconnect event. 3) Raise a disconnect event, connect to the remaining server, raise a reconnect event I observe the following behaviour and just wanted to know, if that is the expected one using Apache Ignite .NET 2.3 (also matches 2.4). If everything started I kill one of the server nodes and sometimes the client is disconnected and reconnects to the remaining server after a while. It does, however, not occur every time I kill one of the servers. In most cases I am successful forcing a reconnect if I do the following: - Start one server and the client (order doesn’t matter) - Start the second server and wait until everything is connected - Kill the first server - Client gets disconnected / reconnected - So: is that the desired behaviour? Thanks in advance, Dome
