Hi Anil,
What do you mean "the results are not same"? It looks like query should
return a single row.
If there would be more than one row in result and order is not specified in
query, then it is possible to get rows in different order due to data
transferred from other nodes asynchronously.
Hi All,
I am getting query too slow warning message while running Yardstick-ignite
benchmark. Not sure why indexed query is slow here.
machine configurations is 4 core CPU with 16 GB ram.
Topology snapshot [ver=1, servers=1, clients=0, CPUs=4, heap=3.5GB]
WARNING: Query execution is too
Hi,If I have multiple-nodes cluster, and I set up a cache interceptor on a cache. the cache mode is partitioned or duplicated. in partition mode, the cache maybe have a backup or not. My question is: when a cache entry is removed, the interceptor will be called once on one node or
Sorry for keep following up on this, but this is becoming a major issue for
us and we need to understand how ignite treats cluster topology when
transaction are running on server nodes. How do clients joining and leaving
the cluster affects txns?
Thanks,
Binti
--
View this message in context:
Hello Alex and thanks for the reply.
i am checking the links you sent. If I do follow the IgniteQueue approach to
put tasks in a distributed queue and have nodes take them for execution, am
I absolutely covered that only one grid node will take an item-task from the
queue? From the example I see,
Thanks Dmitry.
Based on the scenarios I have to deal with (for the time being at least),
using Ignite distributed cache should ne avoided.
However the issue now is that my callables will have to use Spring beans
(services and DAOs) in order to retrieve on their own the data that they
have to
cool - i thought i'd tried that but perhaps screwed it up will have another
look
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/cache-update-from-NET-client-to-Java-cluster-tp11217p11336.html
Sent from the Apache Ignite Users mailing list archive at
Hi,
Looks like you have mixed up Spring XML and .NET config XML.
Moreover, you don't provide any configuration file when starting Ignite
with Ignition.Start();
To work with ODBC from .NET, you have to configure ODBC in a Spring XML
file (NOT app.config) like this:
I was able to run it and reproduce the problem.
If you add "Console.WriteLine("Cache size: " + cache.GetSize());" to the
end of C# program,
you'll see that there are two entries in the cache, because keys from Java
and C# are not considered equal.
To fix the problem, override GetHashCode/Equals
