Re: Failed to activate cluster - table already exists

2018-01-26 Thread Thomas Isaksen
anuary 26, 2018 8:48:58 PM To: user@ignite.apache.org Subject: Re: Failed to activate cluster - table already exists Hi Thomas, Please share with us next time a reproducer with work folder. It's something that should be checked. Did you change your QueryEntities between cluster restart? Thanks

Re: Failed to activate cluster - table already exists

2018-01-26 Thread Michael Cherkasov
riginal Message- > From: Mikhail [mailto:michael.cherka...@gmail.com] > Sent: fredag 26. januar 2018 01.51 > To: user@ignite.apache.org > Subject: Re: Failed to activate cluster - table already exists > > Hi Thomas, > > Looks like you can reproduce the issue with a unit tes

RE: Failed to activate cluster - table already exists

2018-01-26 Thread Thomas Isaksen
- From: Mikhail [mailto:michael.cherka...@gmail.com] Sent: fredag 26. januar 2018 01.51 To: user@ignite.apache.org Subject: Re: Failed to activate cluster - table already exists Hi Thomas, Looks like you can reproduce the issue with a unit test. Could you please share it with us? Thanks, Mike

Re: Failed to activate cluster - table already exists

2018-01-25 Thread Mikhail
Hi Thomas, Looks like you can reproduce the issue with a unit test. Could you please share it with us? Thanks, Mike. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Failed to activate cluster - table already exists

2018-01-25 Thread Thomas Isaksen
I simply stopped my cluster and started it again, when I try to activate I get the following: [12:50:26,308][SEVERE][sys-#38][GridTaskWorker] Failed to obtain remote job result policy for result from ComputeTask.result(..) method (will fail the whole task): GridJobResultImpl [job=C4