@Taras Ledkov <tled...@gridgain.com>, @Igor Seliverstov <iselivers...@gridgain.com>, @Yuriy Gerzhedovich <ygerzhedov...@gridgain.com>, did you guys see this issue before? It looks like a bug in the SQL engine.
Kamlesh, in the meantime, try to follow the procedure described in this JIRA ticket (you need to clean the index that we'll be rebuild on the startup): https://issues.apache.org/jira/browse/IGNITE-11252 Let us know if it worked out for you. We'll document this procedure. - Denis On Wed, Sep 2, 2020 at 10:07 AM Kamlesh Joshi <kamlesh.jo...@ril.com> wrote: > > Hi Tom, > > We are using java 1.8.151 and Ignite 2.7.6. > > Regards, > Kamlesh > > > ------------------------------ > *From:* Tom Black <tom@pobox.store> > *Sent:* Wednesday, 2 September, 2020, 1:31 pm > *To:* user@ignite.apache.org > *Subject:* [External]Re: unable to start node > > The e-mail below is from an external source. Please do not open > attachments or click links from an unknown or suspicious origin. > > Kamlesh Joshi wrote: > > */[2020-08-28T19:05:03,296][ERROR][sys-#940187%EDIFReplica%][] JVM will > > be halted immediately due to the failure: [failureCtx=FailureContext > > [type=CRITICAL_ERROR, err=org.h2.message.DbException: General error: > > "class o.a.i.IgniteCheckedException: Unexpected binary object class > > [type=class java.lang.String]" [50000-197]]]/* > > what ignite and java version are you using? > > regards. > > > > "*Confidentiality Warning*: This message and any attachments are intended > only for the use of the intended recipient(s), are confidential and may be > privileged. If you are not the intended recipient, you are hereby notified > that any review, re-transmission, conversion to hard copy, copying, > circulation or other use of this message and any attachments is strictly > prohibited. If you are not the intended recipient, please notify the sender > immediately by return email and delete this message and any attachments > from your system. > > *Virus Warning:* Although the company has taken reasonable precautions to > ensure no viruses are present in this email. The company cannot accept > responsibility for any loss or damage arising from the use of this email or > attachment." >
