I've done some additional testing. By shutting down another (the last) client node that was running independent code, I was able to purge the bad version of my code from the servers, while leaving the userVersion at "0". Apparently in this case, the client nodes are "master" nodes. (The deployment modes documentation uses the terms "master" and "workers" without defining them, so you are left to guess which nodes are master and how they become one. Because they sent a closure? Because some class was actually loaded from them?).
Running from Eclipse with a local vanilla 2.3 docker image as a single server, changing the userVersion ignite.xml from "0" to "1" on the client causes the error: "Caused by: class org.apache.ignite.IgniteDeploymentException: Task was not deployed or was redeployed since task execution" , even if the server was just restarted. It starts working again of the user version changes back to "0". That is, /changing the userVersion on the client causes the client not to be able to talk to the server./ Since server will cache the userVersion on the first access, there doesn't seem to be a path to get the client's code to redeploy except by shutting down all clients, or by shutting down all servers. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
