Hi Team,
How do you compare Ignite data & compute grid components to OpenMP / MPI?
can you please call out the pros and cons of the two frameworks?
Thanks,
Arthi
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/MPI-OpenMP-compared-to-Ignite-tp4804.html
Sent
facing similar problem : memory consumption problem.
loading 47Millions Records, with data streamer method, took 30mins.
memory usage : 51g.
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Slow-data-loading-and-high-very-memory-usage-issues-tp4798p4803.html
Sent
Hi,
It creates the 'libs' folder. And I got imported the above project also that
you mentioned, but it's still showing the same result! :(
Also, to let you know, I'm using cygwin on a windows platform to run the
script, could that be any reason for it to not run?
--
View this message in
There are several options how you can deal with this:
1) define caches in Spring XML configuration of all server nodes and start near
caches on clients when needed;
2) start a special client that will initialize all required caches dynamically
and stop it after that. The rest of the clients can
Hi, I’m trying to load tSV file size ~six gigabytes (contains ~90 million
records) into single Apache Ignite node with allocated heap size = 40
gigabytes. For loading used IgniteDataStreamer. Code and sample (10
records) of data is here:
https://github.com/olegskoblya/traffic-loader.git
Physical
does write behind work without this setting :-
cacheCfg.setWriteSynchronizationMode(CacheWriteSynchronizationMode.FULL_ASYNC);
Here is my cache setting :-
cacheCfg.setReadThrough(true);
cacheCfg.setWriteThrough(true);
cacheCfg.setWriteBehindEnabled(true);
I undrestand that WriteAll will be called per cache.
But my undrestanding is this :-
1) There are two configs for write behind 1) No of Entries and Time
2) SO if I make three cache entries in three transaction before the time
(which is configured to lets say 4000 ms ) then the writeAll should
Hi, what exactly is not clear?
When you create objects in Java, they end up on JVM heap, in managed
memory. These objects are subject to automatic garbage collection.
Ignite Off-Heap Memory feature stores cache data in unmanaged memory
(manual allocation/deallocation, like you do in C and other
Hi,
Please clarify what are you trying to achieve?
>From logs I see the Ignite grid instance tries to start several times.
Please check the ServletContextListenerStartup class
for example how to correctly start Ignite in the servlet environment:
You can't have on the client node "far" and "near" cache simultaneously.
The error message you get on the attempt is pretty self-explanatory.
So I see not bug here.
2016-05-05 17:13 GMT+03:00 zshamrock :
> Yes, removing definition of the cache from
Hello,
Could someone explain this in simpler way ? Maybe some intuition ?
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Off-Heap-Memory-simpler-explanation-than-in-docs-tp4790.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Hi,
Put all your jars into lib folder if you are using standalone Ignite
distribution.
When you can provide your own config file as described here[1]
[1]
https://apacheignite.readme.io/docs/getting-started#section-passing-configuration-file
2016-05-05 16:32 GMT+03:00 zshamrock
If I have a read/write through enabled, and do implement a CacheStore, and I
use the config file to setup the Ignite.
How do I provide my CacheStore implementation (and the necessary
dependencies, like database driver, and my application specific classes) for
the Ignite instance I run in the
Hi,
By when is the next release v.16 scheduled?
Thanks,
Arthi
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/v1-6-release-date-tp4786.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Hi Vladimir...Yes that is correct. I 1.6 binary that I downloaded from the
Jenkins server did not have your change. However 1.6 source I downloaded
from git branch has your change. I am building that and see if I can get
rid of the error.
Thanks,
Murthy.
On Wed, May 4, 2016 at 4:30 AM, Vladimir
Hi!
We have an open issue for this:
https://issues.apache.org/jira/browse/IGNITE-369
For now the only way to enable cache metrics - via configuration on cache
startup.
You may watch issue IGNITE-369 in JIRA and will be notified when it will be
fixed.
But I'm afraid it will not be fixed in nearest
So, it is not recommended to turn them on in production?
Then how you measure you cache overall behavior?
Could be it controlled over JMX?
--
View this message in context:
Hello,
Yes, cache metrics not work by default for performance reason. You can
enable it throught cache configuration property
javax.cache.configuration.MutableConfiguration#setStatisticsEnabled (or into
xml )
--
View this message in context:
Great!
--
View this message in context:
http://apache-ignite-users.70518.x6.nabble.com/Is-it-possible-from-ignitevisor-to-say-which-nodes-are-server-nodes-and-which-are-client-tp4770p4779.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
19 matches
Mail list logo