Failing to deploy service

Hi, I am trying to deploy a service during ignite node startup. But I noticed 2 peculiar behaviours. I am loading the class using Note that I am using a single-node cluster. Thus, the service class is present on the classpath of the node where I am trying to deploy this service.

Re: 2.4.0 with Tomcat 8.5 and Java 9

Eric, Glad it helped! And no, I guess that won’t be unique only for your environment. Thanks for sharing your successful run configuration — hope it helps other users adopt Ignite to theirs environment as mush as it possible for now. Also, if possible, please, share with us the results of web

Re: stop sending messages pls

test message 2018-04-02 10:12 GMT+03:00 andriy.kasat...@kyivstar.net < andriy.kasat...@kyivstar.net>: > My email is andriy.kasat...@kyivstar.net. Can you please unsubscribe this > mail. >

Re: Broadcast method fails with DataStorage peristenceEnabled

I found what I posted on our internal slack at the time, suggesting that I thought this was a library version mismatch. "I’m getting some pretty squirrelly behavior. I’m using maven to build/run the test on the client node. I was trying to fix the logging issue below (which was not blocking).

Re: Broadcast method fails with DataStorage peristenceEnabled

I verified the java version is the same. The interesting thing here is the code runs correctly if I disable persistence. I wonder whether there is an issue in enabling persistence or I am doing something wrong here. On Tue, Apr 3, 2018 at 12:12 PM, David Harvey wrote: >

Re: Broadcast method fails with DataStorage peristenceEnabled

PS. I'm actually remembering it was due to a mismatch of Java7 vs 8, which does not make that much sense, because we have been running Java7 clients recently with no issues. On Tue, Apr 3, 2018 at 3:05 PM, David Harvey wrote: > I had those "UNKNOWN PAIR" issues early

Re: Broadcast method fails with DataStorage peristenceEnabled

I had those "UNKNOWN PAIR" issues early on, and it seemed to be some kind of version problem, like the client was not running at the same rev. On Tue, Apr 3, 2018 at 2:15 PM, Supun Nakandala wrote: > Hi all, > > I am trying to setup Apache Ignite with persistence

Re: Broadcast method fails with DataStorage peristenceEnabled

The error that I get is this: *Apr 03, 2018 11:56:17 AM org.apache.ignite.logger.java.JavaLogger error* *SEVERE: Failed to obtain remote job result policy for result from ComputeTask.result(..) method (will fail the whole task): GridJobResultImpl [job=C4 [r=Main$$Lambda$2/882646447@4ea7d8ff],

Broadcast method fails with DataStorage peristenceEnabled

Hi all, I am trying to setup Apache Ignite with persistence enabled and facing a deserialization failure when executing broadcast method with data storage persistence enabled. The following code will recreate this problem: public static void main(String[] args) throws IOException {

Re: 2.4.0 with Tomcat 8.5 and Java 9

Petr, Thanks for tip. This is looking very promising as I see Ignite starting in the catalina.out file now. As a note, I added those directives to my bin/setenv.sh script as JAVA_OPTS as opposed to JVM_OPTS as that didn't seem to work. Also, I did have to add the cache-api-1.1.0.jar file to my

Re: One time replicating of the cluster data for setting up a new cluster

We had done this to group all of the data that needs to be backed up onto the SSD. Work also contains the log directory, and I haven't seen how to put that elsewhere.

Re: How to query cache with sql commands

Hello Ivan! Note that you can also call setQueryEntities() from Java code, or add indexedTypes to XML file! You should have complete freedom here. Regards, -- Ilya Kasnacheev 2018-04-03 14:18 GMT+03:00 Denis Mekhanikov : > Hi Ivan! > > You should also add *QueryEntity*

Re: How to query cache with sql commands

Hi Ivan! You should also add *QueryEntity* configuration to XML file, or use *CacheConfiguration#setIndexedTypes()* method from Java code. After that you will be able to query data, that was added to your caches. And you won't actually need to create tables, using DDL, they will be created by

Re: One time replicating of the cluster data for setting up a new cluster

When using Ignite Persistence, I have found that you can simply replicate the folders, if you deactivate the cluster first. You need the wal and store, as well as two folders under $IGNITE_HOME/work which are named something like marshaller* and binary* On Tue, Apr 3, 2018 at 2:52 AM, Naveen

Re: Put data(key, obj/table) into one cache

Rick, This code is not compilable, because you are trying to access a non-static class from static method. You should make OneFeature class *static* to let it be referenced from static context. Its declaration should be as follows: *public static class OneFeature* Denis вт, 3 апр. 2018 г. в

Put data(key, obj/table) into one cache

Dear all, I would like to put data(key, obj/table) into one cache, as public class WriteTable { public class OneFeature { @QuerySqlField (index = true) /** Field will NOT be accessible from DML statements. */ private final String test; public OneFeature(String test) { this.test = test;

Re: Any idea what this is ?

Hi! I am not 100% sure but I think it could be related to a mistake by me, in the service init() method I had a reference to another object that returned the ignite instance, but this is not initialized until after the Ignite.start() finish so may not be initialized when services are started

How to query cache with sql commands

Hi, ignite users. I am a complete beginner when it comes to Apache Ignite. I am not a java programmer either. I am experimenting with a simple ignite setup, latest version 2.4.0, binary distribution on linux x86_64. I only have one partitioned cache, called default. I was able to insert keys

Re: 2.4.0 with Tomcat 8.5 and Java 9

Hi, Eric. Try to add to Tomcat’s JVM_OPTS following directives, please: --add-exports java.base/jdk.internal.misc=ALL-UNNAMED --add-exports java.base/sun.nio.ch=ALL-UNNAMED --add-exports java.management/com.sun.jmx.mbeanserver=ALL-UNNAMED --add-exports

One time replicating of the cluster data for setting up a new cluster

Hi Am using 2.3 I do have one cluster running with 3 servers, each with 2 nodes. Now we need to replicate this data on a new cluster which is going to have the same configuration. Just copying node folders enough to get the data ? Whats the best practice for doing this Thanks Naveen --

Re: Running heavy queries on Ignite cluster on backing store directly without impacting the cluster

Hi ANdrew There were cases, when I just run select * from table on SQLLINE unknowingly, we could see queries getting slowed down and OOM errors. Our dev machines not very high end ones. When we deliver this solution, production support guys can run queries to debug any data related issues,