Cross-posting from SO: As a rule you should not perform cache operations, or most of other operations that block or access Ignite internals. Events should be very fast and lightweight, meaning that they are executed from inside Ignite threads and Ignite internal locks.
Just schedule an operation in a different thread on event arrival. Regards, -- Ilya Kasnacheev пн, 12 нояб. 2018 г. в 10:17, aealexsandrov <[email protected]>: > Hi, > > The cache could be started but possible cluster wasn't activated yet. Could > you please provide some information: > > 1)Did you see warnings or errors in the log? > 2)Did you see this issue on normal cluster start or only on client restart? > > Also, I see that you use it in the class named server config. Could you > please also provide the use case of this class? > > BR, > Andrei > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
