Really appreciate for your reply, Andrei.
Now I understand why the result didn't store on the same node where it was
calculated. I will try your suggestions.
But there still remain a problem that job b,d,f were calculated on Node_B,
the results were lost. No partitions store these jobs' results.
Are there any exceptions on startup?
-Val
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Hey Stanislav,
I was able to get into a situation like described before but the server nodes
are not under pressure any more. The cache state seems to stay corrupted. I was
able to restart the client and even then the client does not see the whole
cache content (but with the sql query) and gets
Hi,
Blocked threads show only the fact that there are no tasks to process in
pool. Do you use persistence and/or indexing? Could you please attach your
configs and logs from all nodes? Please take few sequential thread dumps
when throughput is low.
Thanks!
-Dmitry
--
Sent from:
Hi,
Could you please share your configuration files, cache configurations, logs
from all nodes and the code snippets you use to do the queries (visor
commands, SQL, etc)?
Thanks,
Stan
Bellenger, Dominique wrote
> Hey Igniters,
>
> I've the following setup (Ignite .NET 2.4): 2 Server nodes, 1
Hi Michael,
As I see from your configuration you are going to have cluster with two
ignite servers and PARTITIONED cache.
You can't choose directly on what node will be stored your cache entities
because ignite will use its own affinity function that will maps keys to
partitions (not nodes).
In
I have a node running in AWS launched from the apache ignite ami which runs
ignite in a docker container. The ignite container runs. However, it does not
register it's ip in the discovery S3 bucket. Can anyone that has this running
in AWS let me know what I'm missing here?
I created a public
Greetings,
We've been running a large, high volume, low latency Ignite Compute Grid in
Production for a few months now, and, in general, things are going quite
well.
But we see a handful of large spikes a day in our application (approx. 1 per
hour)
And thus far we've been at a loss as to explain
Hello!
For that, you can use keyConfiguration property on igniteCache:
It is poorly documented, unfortunately, I've raised submit a ticket about
that:https://issues.apache.org/jira/browse/IGNITE-8253
Regards,
--
Sent from:
Hi, all! I am trying to use the computegird of ignite to do some compute job,
but I met a problem.
I started two server nodes(different host) to form a clustergroup. Node_A
was started by eclipse, Node_B was started by ignite.cmd, two nodes had the
same configurations except heap size(Node_A
Hey Igniters,
I've the following setup (Ignite .NET 2.4): 2 Server nodes, 1 client node doing
SQL-queries on the cache periodically (every 20 Seconds in my case).
The cache is filled with 110_000 entries from a database, using "LoadCache"
method. Key is a string representation of a number,
Dear Sam and Nikolai,
My case is similar to this one (Performance with increase in node) .
So, could you tell me how to deal with this problem about decreasing
performances of cache with multi nodes?
If any idea could be shared with me, I highly appreciate it.
Rick
From: linr...@itri.org.tw
Hi Roman,
I think that my case is similar to this one:
http://apache-ignite-users.70518.x6.nabble.com/Performance-with-increase-in-node-td9378.html
(Performance with increase in node)
From those discussions, I found the two tips to properly use cache in ignite
node.
1. Cache has to be
How do you configure affinityKey in apache ignite and implement the Join
between multiple partition caches after the JDBC client connects to the
cluster?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
14 matches
Mail list logo
