Yes Sir, that exception is from my code that has caused ignite2 (second ignite node) to go offline :) Investigating now ...
-- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Yes Sir, that exception is from my code that has caused ignite2 (second ignite node) to go offline :) Investigating now ...
-- Sent from: http://apache-ignite-users.70518.x6.nabble.com/