Hi,
I am running Ignite 2.3 using Cassandra as my persistence store.
I got unmarshall error when a server node trying to unmarshall an object of old
version from Cassandra.
This is the scenario:
1. Object of ClassA (older version) is serialized and persisted into
Cassandra
2.
г. 2018 г. в 14:33, Calvin KL Wong, CLSA
mailto:calvin.kl.w...@clsa.com>>:
Hi,
I deployed a service from a client node to our grid using the following code:
IgniteCluster cluster = ignite.cluster();
ClusterGroup group = cluster.forAttribute(…);
Ignite.services(workerGroup).deployClus
Hi,
I deployed a service from a client node to our grid using the following code:
IgniteCluster cluster = ignite.cluster();
ClusterGroup group = cluster.forAttribute(...);
Ignite.services(workerGroup).deployClusterSingleton("blaze/hsbc")
It is fine most of the time. However we just encountered
Hi,
Is there any mbean to get all deployed services in a grid (or in a node)?
Thanks,
Calvin
Calvin KL Wong
Sr. Lead Engineer, Execution Services
D +852 2600 7983 | M +852 9267 9471 | T +852 2600
5/F, One Island East, 18 Westlands Road, Island East, Hong Kong
[:1. Social Media
ct: Re: Service not found for a deployed service
Calvin,
Did Service#init() method throw any exceptions?
If so, then you would see the same problem.
Denis
пт, 3 авг. 2018 г. в 14:13, Calvin KL Wong, CLSA
mailto:calvin.kl.w...@clsa.com>>:
Actually, we deployed the service at 02:00, and didn’t use
Got it, thanks for the info.
Thanks,
Calvin
-Original Message-
From: dkarachentsev [mailto:dkarachent...@gridgain.com]
Sent: Monday, July 16, 2018 9:57 PM
To: user@ignite.apache.org
Subject: RE: Best practice for class versioning: marshaller error
Hi Calvin,
> Can I assume that
Hi,
I encountered a scenario where my process was blocked at a call to
deployClusterSingleton.
IgniteServices svcs = ignite.services();
svcs.deployClusterSingleton(..., ...);
Too bad that I didn't get the stack trace.
I didn't specify any node filter. I was able to deploy the service upon
Hi,
I have a cache of .
I found that when I use a ScanQuery on that cache, result will be deserialized
using OptimizedMarshaller; Ignite sends 'ordered' message using
GridCacheQueryResonseEntry. Whereas if I use ContinousQuery, result will be
deserialized using BinaryMarshaller.
My problem
that there is a problem in using BinaryMarshaller.
Thanks,
Stan
From: Calvin KL Wong, CLSA<mailto:calvin.kl.w...@clsa.com>
Sent: 9 июля 2018 г. 13:40
To: user@ignite.apache.org<mailto:user@ignite.apache.org>
Subject: RE: OptimizedMarshaller instead of BinaryMarshaller is used
forS
: Calvin KL Wong, CLSA [mailto:calvin.kl.w...@clsa.com]
Sent: Monday, July 09, 2018 11:50 AM
To: user@ignite.apache.org
Subject: OptimizedMarshaller instead of BinaryMarshaller is used for ScanQuery
Hi,
I have a cache of .
I found that when I use a ScanQuery on that cache, result
Then I am confused with the exception I got. Please bear with me.
I believe what happened was a client (with a new version of user class) trying
to deserialize an old object (an old version of user class) from Continuous
Query.
This was what happened base on the log:
1. GridCacheIoManager
Thanks, Dmitry.
>>2-3. In your case, you have and java.time.Ser in one of the fields of your
>>POJO (or maybe inside of depended object), and it is Externalizable. In such
>>case BinaryMarshalelr falls back to OptimizedMarshaller with all the issues.
>>Try to remove it from your POJOs or make
Hi Dmitry,
Thanks for your response!
I want to confirm my understanding -
If I disable compact footer and add your POJOs in BinaryConfiguration, I will
be deserialize back the serialized object after I stop grid and removed the
local files that hold the marshaller cache (I believe they are
13 matches
Mail list logo