Hi there, I have an application that use ignite for caching purposes. Basically one module is responsible of keeping the cache fresh and then I have clients that consume the cache. When I use a continuous query the read/write performance of the cluster is affected a lot (10x slower). Are there any configurations that might help, is this normal? Thanks!
Posted by Florin B about a year ago
I am new to Apache Ignite. I have an application for which I am trying to utilize Apache Ignite for a distributed cache. I now have 3 servers to process the information and if one server is down, one of the other two servers need to handle the request. I have configured the "REPLICATED" cache in the Cache Configuration and have configured the required IP Address using "TcpDiscoveryVmIpFinder". The topology snapshot always shows me one client and one server regardless if all three servers are up, and killing one server disconnects the client node even if the other two servers are up.
Posted by Nikhil Samuel about a year ago
I want to make sure some objects that are persisted in the database, once they are persisted they are immediately evicted from the Ignite grid. Is there a possibility to listen to write-behind events, identify which objects were persisted, then based on their attributes and/or some configured policy decide to evict or not ?
Posted by Dorel Matei about a year ago
I want to make sure some objects that are persisted in the database, once they are persisted they are immediately evicted from the Ignite grid. Is there a possibility to intercept write-behind events, identify which objects were persisted, then based on their content attributes decide if they are "evictable", then evict them ?
Posted by Dorel Matei about a year ago
Hi all, I am trying to start a server using the `ignite.sh` script and am getting the above error (failed to load HadoopV2Job). "config/default-config.xml" is being passed to CommandLineStartup and hasn't been changed. Has anyone came across this issue or does anyone know how to fix it? My Ignite version is 1.4.0 and here is the full stack trace: class org.apache.ignite.IgniteException: Failed to start processor: HadoopProcessor [idCtr=0] at org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:881) at org.apache.ignite.Ignition.start(Ignition.java:349) at org.apache.ignite.startup.cmdline.CommandLineStartup.main(CommandLineStartup.java:302) Caused by: class org.apache.ignite.IgniteCheckedException: Failed to start processor: HadoopProcessor [idCtr=0] at org.apache.ignite.internal.IgniteKernal.startProcessor(IgniteKernal.java:1504) at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:888) at org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1617) at org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1484) at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:965) at org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:892) at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:784) at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:705) at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:576) at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:546) at org.apache.ignite.Ignition.start(Ignition.java:346) ... 1 more Caused by: class org.apache.ignite.IgniteCheckedException: Failed to load job class [class=org.apache.ignite.internal.processors.hadoop.v2.HadoopV2Job] at org.apache.ignite.internal.processors.hadoop.jobtracker.HadoopJobTracker.start(HadoopJobTracker.java:167) at org.apache.ignite.internal.processors.hadoop.HadoopProcessor.start(HadoopProcessor.java:103) at org.apache.ignite.internal.IgniteKernal.startProcessor(IgniteKernal.java:1501) ... 11 more Caused by: java.lang.IllegalArgumentException at org.objectweb.asm.ClassReader.<init>(Unknown Source) at org.objectweb.asm.ClassReader.<init>(Unknown Source) at org.objectweb.asm.ClassReader.<init>(Unknown Source) at org.apache.ignite.internal.processors.hadoop.HadoopClassLoader.hasExternalDependencies(HadoopClassLoader.java:288) at org.apache.ignite.internal.processors.hadoop.HadoopClassLoader.loadClass(HadoopClassLoader.java:162) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at org.apache.ignite.internal.processors.hadoop.jobtracker.HadoopJobTracker.start(HadoopJobTracker.java:163) ... 13 more
Posted by Shane Kinsella about a year ago
I am using a servlet to initialize or get an ignite grid during init. During tomcat shutdown there are some thread locals which are not cleaned and tomcat print warning leading to potential memory leak. Can I add Iginition. stop or Ignite.close in my destruct method in servlet. If i add this there will it shuts down for all the nodes???
Posted by Sahil Narwal about a year ago
This is my code which I m using> I have started ignite on a server and passing on the respective IP in the following to cache specific data. But I m seeing following error class org.apache.ignite.IgniteException: Default grid instance has already been started. String cacheId = "partitioned"; TcpDiscoverySpi spi = new TcpDiscoverySpi(); TcpDiscoveryVmIpFinder ipFinder = new TcpDiscoveryVmIpFinder(); ipFinder.setAddresses(Arrays.asList(serverIP)); spi.setIpFinder(ipFinder); IgniteConfiguration cfg = new IgniteConfiguration(); cfg.setDiscoverySpi(spi); CacheConfiguration cacheCfg = new CacheConfiguration(); cacheCfg.setName(cacheId); cacheCfg.setCacheMode(CacheMode.PARTITIONED); cfg.setCacheConfiguration(cacheCfg); Ignition.setClientMode(true); System.out.println("cfg=="+cfg); Ignite ignite = Ignition.start(cfg); IgniteCache<String, String> cache = ignite.getOrCreateCache("ServerCache"); cache.put(DataFileName, fileData); //store ignite.close();
Posted by Bhargav about a year ago
I need to create an architecture for Ignite that allows: Data to be streamed into a cache. A cache listener to put selected entries in a queue. One or more processes wait for queue entries, do some work and put the results back in a cache. Please can somebody describe the Ignite functionality that would be required to do this. Also, point me in the direction of an example(s) of a listener putting something on a queue and 1 or more processes consuming the queue entries. Many thanks, Andy
Posted by Andy Rendle about a year ago
Hi , I am new to ignote/gridgain. Trying to do a small experiment with ignite. I am tryign a clinet server setup. I have setup a ignite server node on a VM and also setup a client node on my laptop.using ignote.sh script I have started botht he nodes and they are discovered correctly. Now I want to use this client node which is running thru my java code. Is it possible ? I dont want to start the ignite thru my java code using ignote.start() method. Regards, Vamsi
Posted by Vamsi about a year ago
In all examples visorcmd can be connected to application by putting path to XML configuration as start parameter. But my application configured by Java-code and has no one XML file. It is real to connect Visor to this application?
Posted by Skalsky Andrey about a year ago
I am creating a cache with a CacheStoreFactory implementation and a CacheStoreSessionListener. If I set the CacheConfiguration with these fields and then call createCache but in an INSTANCE method I get this exception: Exception in thread "main" javax.cache.CacheException: class org.apache.ignite.IgniteCheckedException: Failed to validate cache configuration (make sure all objects in cache configuration are serializable): LongCache In a static method, this does not occur. This can be easily reproduced by modifying the CacheJdbcStoreExample.java in examples. This is happening under Ignite 1.30
Posted by Michael G about a year ago