1. I had created IGNITE-7905 for this interaction with userVersion and
perhaps only ignite.Activate() issued from the client. I think it deals
with the code for Activate() using nested classes. The server decided that
it already had a version of the ignite code loaded, and wasn't goin
Hello Dave!
I suggest filling an issue agains Apache Ignite JIRA with this scenario and
suggestions about how it should work after fix. Test case would be awesome.
Regards,
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Unsubscribe
On Tue, Feb 20, 2018 at 1:09 PM Dave Harvey wrote:
> 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".
> Ap
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
deploym
I was trying to demonstrate changing classes on a client node so that classes
on servers get replaced with new code, but the symptoms make me believe that
I don't understand the rules at all.
The deployment mode is SHARED. I read the instructions and creates an
ignite.xml with a different user
