Thin client before version 2.9 throws an exception when there is more
than one scheme with the same type name and compact footers are enabled.
The scheme is a set of field names of the object, so, using only one scheme
per type (if it's possible in your case) will solve the problem.
If you don't wa
Thanks Alex..
Here it says it throws this exception when ignite does not find this record
In our case, data exists and it get resolved if we do a node restart
And, any work-around we have to fix this issue with current version ignite
2.8.1
Thanks
On Mon, Nov 22, 2021 at 12:20 PM Alex Plehanov
Hello!
Most probably it's related to ticket [1] that is fixed in 2.9 release.
[1]: https://issues.apache.org/jira/browse/IGNITE-13192
пн, 22 нояб. 2021 г. в 03:11, Naveen Kumar :
> Hi All
>
> We are using 2.8.1
> At times, we do get this BinaryObjectException while calling GETs thru
> thin clie
Hello,
Most probably it's related to [1], which is fixed since Ignite 2.9.1.
[1]: https://issues.apache.org/jira/browse/IGNITE-13401
чт, 19 авг. 2021 г. в 09:53, Naveen Kumar :
> Hi All
>
> We are using Ignite 2.8.1 and using the thin clients majorly.
> Facing a strange issues for last couple o
Hello!
I guess this information was stored somewhere and is causing conflicts now.
You can try dropping binary_meta/ directory from ignite work dir on all
nodes, hope that it would be repopulated all right. Make sure to back it up
first!
Regards,
--
Ilya Kasnacheev
чт, 25 февр. 2021 г. в 21:21
Hello!
Currently it is not implemented. Metadata will be preserver unless cluster
is restarted (in case persistence is enabled, unless it is cleared)
Regards,
--
Ilya Kasnacheev
вс, 7 июн. 2020 г. в 02:32, Andrew Munn :
> So once I insert an instance of a class in a Map I can't change the typ
So once I insert an instance of a class in a Map I can't change the type of
any existing member variable in the class, even if I clear the map?
Seems like there should be some programatic way to clear any left-over
class metadata/schema if simply clearing the cache won't do it. Right?
On Sat, Jun
You might have hit the following specificity ("Cluster Doesn’t Start After
Field Type Changes") that happens if you change a type of a field:
https://www.gridgain.com/docs/latest/perf-troubleshooting-guide/troubleshooting#cluster-doesnt-start-after-field-type-changes
-
Denis
On Fri, Jun 5, 2020
Vladislav,
Actually I don't know the exact object that causes the deserialization
problem. For me it looks like a remote call fails.
If I have to use some workaround, I prefer switching off the compact
footers.
Dmitry.
--
View this message in context:
http://apache-ignite-users.70518.x6.nabbl
Dmitry,
You can to try execute build() for the specific object:
BinaryObject operation = ignite.binary()
.builder("SomeObject")
.setField("FIELD", value)
.build();
(or something similar for java object)
after the client reconnected. In
Hi,
This could be if in client discovery configuration only one server node
address set, that is restarted. In this case clients are unsuccessful in
connecting to stopped node and are shutting down.
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/BinaryObjectExc
Hi val (valery? :)),
Thanks for reply.
Yes, switching off compact footer helped me in this case.
But the whole issue seems strange - my client stops working after a single
node cluster is restarted. To make the whole system working I have to
restart all my clients.
Is this the behavior that is ex
Dmitry,
Basically this exception means that you tried to deserialize a binary object
that was never serialized on this cluster. When a type is serialized for the
first time, Ignite saves the meta data for this type in a system cache, so
once you deserialize this object (potentially on a different
Hi,
Could you please provide a reproduction example?
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/BinaryObjectException-after-Ignite-restarts-tp9552p9558.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Hi Yuci,
This is correct behavior, Ignite does not allow to change the type of
existing field. This is because you can have instances of two versions at
the same time, and after such change you will not be able to deserialize old
object on new node or other way around. You can add new fields thoug
15 matches
Mail list logo
