Cache Node Concept
Hi, Can we refer a cache instance running on a Ignite server as a node or cache node ? Say, a cache is distributed over various Ignite servers, so can we call each instance in a server as node or cache node ? Regards Abhishek
Re: jvm setting to turn off the Garbage collector
Thanks Val for your response. We want to perform some memory analysis. Regards Abhishek On Wed, Oct 26, 2016 at 2:47 PM, vkulichenko wrote: > Hi Abhishek, > > If you disable GC, you will run out of memory very quickly. Can you please > clarify why you want to do this? > > -Val > > > > -- > View this message in context: http://apache-ignite-users.705 > 18.x6.nabble.com/jvm-setting-to-turn-off-the-Garbage- > collector-tp8508p8520.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. >
jvm setting to turn off the Garbage collector
Hi, Is there any specific setting to turn off the Garbage collector in JVM that is invoked from C++ application? Regards Abhishek
Re: zero downtime while upgrade
Thanks Denis for the information. Regards Abhishek On Fri, Oct 21, 2016 at 4:16 PM, Denis Magda wrote: > Hello Abhishek, > > It will not work as well. Only the nodes with the same Apache Ignite > version can co-exist in a single cluster. > > — > Denis > > On Oct 21, 2016, at 8:11 AM, Abhishek Jain > wrote: > > Thanks for your very quick reponse. > > But is it possible that within the same cluster if we can run multiple > versions of apache ignite nodes on different host machines ? > > Regards > Abhishek > > On Fri, Oct 21, 2016 at 8:37 AM, Vladislav Pyatkov > wrote: > >> Hi, >> >> Unfortunately not, because changes between Ignite version often going >> with feature of architecture. >> >> GridGain supports rolling-upgardes[1], but this works for minor version >> only. >> >> >> [1]: https://gridgain.readme.io/docs/rolling-upgardes >> >> On Fri, Oct 21, 2016 at 3:50 PM, Abhishek Jain < >> mail.abhishekj...@gmail.com> wrote: >> >>> Hi Folks, >>> >>> Does apache Ignite supports zero downtime while upgrading to new version >>> ? >>> >>> Regards >>> Abhishek >>> >> >> >> >> -- >> Vladislav Pyatkov >> > > >
Re: zero downtime while upgrade
Thanks for your very quick reponse. But is it possible that within the same cluster if we can run multiple versions of apache ignite nodes on different host machines ? Regards Abhishek On Fri, Oct 21, 2016 at 8:37 AM, Vladislav Pyatkov wrote: > Hi, > > Unfortunately not, because changes between Ignite version often going with > feature of architecture. > > GridGain supports rolling-upgardes[1], but this works for minor version > only. > > > [1]: https://gridgain.readme.io/docs/rolling-upgardes > > On Fri, Oct 21, 2016 at 3:50 PM, Abhishek Jain < > mail.abhishekj...@gmail.com> wrote: > >> Hi Folks, >> >> Does apache Ignite supports zero downtime while upgrading to new version ? >> >> Regards >> Abhishek >> > > > > -- > Vladislav Pyatkov >
zero downtime while upgrade
Hi Folks, Does apache Ignite supports zero downtime while upgrading to new version ? Regards Abhishek
Re: Automatic Persistence Example - Demo
Thanks Denis, it worked!!! you made my day.
I appreciate your efforts and suggestions.
Regards
Abhishek
On Tue, Sep 13, 2016 at 11:43 AM, Denis Magda wrote:
> Looks like CLASSPATH env variable is ignored on this Linux distribution
> side. You should refer to basic documentation from Oracle (JRE/JDK owner)
> or use ignite.sh script in the following way:
>
>
>1. add MAIN_CLASS env variable referring to Demo class (export
>MAIN_CLASS=org.apache.ignite.schema.Demo)
>2. add ignite-examples jar into {apache}/libs folder
>3. execute ignite.sh script. Refer to the source of ignite.sh for more
>details on how the classpath is prepared and MAIN_CLASS is used
>
>
> —
> Denis
>
> On Sep 12, 2016, at 4:11 PM, Abhishek Jain
> wrote:
>
> Thanks Denis for your quick response. Our requirement is to make it work
> in the linux command line. The method mentioned in the Automatic
> Persistence page, is to import the pom.xml from the IDE and execute the
> Demo.java. With Eclipse in Windows is working. To take it to the next step
> I am trying to build and execute from the linux, where the jar file is
> creating but NOT able to execute the Demo application.
>
> I hope you sugested to add the /libs folder as the class
> path, that I had already included (*as part of the environment variable
> CLASSPATH*) and checked which is giving the "no main menifest attribute"
> error, please see my previous post for the console output.
>
>
> [root@dbtestvm1 target]# echo $CLASSPATH
> /root/ignite/apache-ignite-fabric-1.6.0-bin/libs:/usr/java/
> default/jre/lib/
> [root@dbtestvm1 target]#
> [root@dbtestvm1 target]# java -jar ignite-examples-1.6.0.jar
> org.apache.ignite.schema.Demo
> no main manifest attribute, in ignite-examples-1.6.0.jar
>
>
> Please correct me if I misunderstood your suggestion.
>
> Regards
> Abhishek
>
>
>
> On Mon, Sep 12, 2016 at 5:02 PM, Denis Magda wrote:
>
>> Alternatively, you can follow this guide [1] that relies on
>> ignite-schema-import.sh script that does all the work for you.
>>
>> [1] https://apacheignite.readme.io/docs/automatic-persistence#demo
>>
>> —
>> Denis
>>
>> On Sep 12, 2016, at 2:58 PM, Denis Magda wrote:
>>
>> Hi,
>>
>> You need to add all the libs that are located in “apache-version/libs”
>> folder to your classpath.
>>
>> —
>> Denis
>>
>> On Sep 12, 2016, at 2:46 PM, Abhishek Jain
>> wrote:
>>
>> Hi,
>>
>> Not able to execute the Demo example given in the Automatic Persistence
>> from the command line in linux. Below is the console output, please let me
>> know if I am missing out anything. I tried couple of ways below with NO
>> success
>>
>> ===
>>
>> [root@dbtestvm1 target]# java -classpath ignite-examples-1.6.0.jar
>> org.apache.ignite.schema.Demo
>> Error: A JNI error has occurred, please check your installation and try
>> again
>> Exception in thread "main" java.lang.NoClassDefFoundError:
>> javax/cache/configuration/Factory
>> at java.lang.Class.getDeclaredMethods0(Native Method)
>> at java.lang.Class.privateGetDeclaredMethods(Class.java:2701)
>> at java.lang.Class.privateGetMethodRecursive(Class.java:3048)
>> at java.lang.Class.getMethod0(Class.java:3018)
>> at java.lang.Class.getMethod(Class.java:1784)
>> at sun.launcher.LauncherHelper.validateMainClass(LauncherHelper.java:544)
>> at sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:526)
>> Caused by: java.lang.ClassNotFoundException:
>> javax.cache.configuration.Factory
>> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
>> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
>> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
>> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
>> ... 7 more
>> [root@dbtestvm1 target]#
>> [root@dbtestvm1 target]#
>> [root@dbtestvm1 target]#
>> [root@dbtestvm1 target]#
>> [root@dbtestvm1 target]# echo $CLASSPATH
>> /root/ignite/apache-ignite-fabric-1.6.0-bin/libs:/usr/java/
>> default/jre/lib/
>> [root@dbtestvm1 target]#
>> [root@dbtestvm1 target]# java -jar ignite-examples-1.6.0.jar
>> org.apache.ignite.schema.Demo
>> no main manifest attribute, in ignite-examples-1.6.0.jar
>> [root@dbtestvm1 target]#
>> [root@dbtestvm1 target]#
>>
>> ==
>>
>> Regards
>> Abhishek
>>
>>
>>
>>
>
>
Re: Automatic Persistence Example - Demo
Thanks Denis for your quick response. Our requirement is to make it work in the linux command line. The method mentioned in the Automatic Persistence page, is to import the pom.xml from the IDE and execute the Demo.java. With Eclipse in Windows is working. To take it to the next step I am trying to build and execute from the linux, where the jar file is creating but NOT able to execute the Demo application. I hope you sugested to add the /libs folder as the class path, that I had already included (*as part of the environment variable CLASSPATH*) and checked which is giving the "no main menifest attribute" error, please see my previous post for the console output. [root@dbtestvm1 target]# echo $CLASSPATH /root/ignite/apache-ignite-fabric-1.6.0-bin/libs:/usr/java/default/jre/lib/ [root@dbtestvm1 target]# [root@dbtestvm1 target]# java -jar ignite-examples-1.6.0.jar org.apache.ignite.schema.Demo no main manifest attribute, in ignite-examples-1.6.0.jar Please correct me if I misunderstood your suggestion. Regards Abhishek On Mon, Sep 12, 2016 at 5:02 PM, Denis Magda wrote: > Alternatively, you can follow this guide [1] that relies on > ignite-schema-import.sh script that does all the work for you. > > [1] https://apacheignite.readme.io/docs/automatic-persistence#demo > > — > Denis > > On Sep 12, 2016, at 2:58 PM, Denis Magda wrote: > > Hi, > > You need to add all the libs that are located in “apache-version/libs” > folder to your classpath. > > — > Denis > > On Sep 12, 2016, at 2:46 PM, Abhishek Jain > wrote: > > Hi, > > Not able to execute the Demo example given in the Automatic Persistence > from the command line in linux. Below is the console output, please let me > know if I am missing out anything. I tried couple of ways below with NO > success > > === > > [root@dbtestvm1 target]# java -classpath ignite-examples-1.6.0.jar > org.apache.ignite.schema.Demo > Error: A JNI error has occurred, please check your installation and try > again > Exception in thread "main" java.lang.NoClassDefFoundError: > javax/cache/configuration/Factory > at java.lang.Class.getDeclaredMethods0(Native Method) > at java.lang.Class.privateGetDeclaredMethods(Class.java:2701) > at java.lang.Class.privateGetMethodRecursive(Class.java:3048) > at java.lang.Class.getMethod0(Class.java:3018) > at java.lang.Class.getMethod(Class.java:1784) > at sun.launcher.LauncherHelper.validateMainClass(LauncherHelper.java:544) > at sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:526) > Caused by: java.lang.ClassNotFoundException: javax.cache.configuration. > Factory > at java.net.URLClassLoader.findClass(URLClassLoader.java:381) > at java.lang.ClassLoader.loadClass(ClassLoader.java:424) > at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) > at java.lang.ClassLoader.loadClass(ClassLoader.java:357) > ... 7 more > [root@dbtestvm1 target]# > [root@dbtestvm1 target]# > [root@dbtestvm1 target]# > [root@dbtestvm1 target]# > [root@dbtestvm1 target]# echo $CLASSPATH > /root/ignite/apache-ignite-fabric-1.6.0-bin/libs:/usr/ > java/default/jre/lib/ > [root@dbtestvm1 target]# > [root@dbtestvm1 target]# java -jar ignite-examples-1.6.0.jar > org.apache.ignite.schema.Demo > no main manifest attribute, in ignite-examples-1.6.0.jar > [root@dbtestvm1 target]# > [root@dbtestvm1 target]# > > == > > Regards > Abhishek > > > >
Automatic Persistence Example - Demo
Hi, Not able to execute the Demo example given in the Automatic Persistence from the command line in linux. Below is the console output, please let me know if I am missing out anything. I tried couple of ways below with NO success === [root@dbtestvm1 target]# java -classpath ignite-examples-1.6.0.jar org.apache.ignite.schema.Demo Error: A JNI error has occurred, please check your installation and try again Exception in thread "main" java.lang.NoClassDefFoundError: javax/cache/configuration/Factory at java.lang.Class.getDeclaredMethods0(Native Method) at java.lang.Class.privateGetDeclaredMethods(Class.java:2701) at java.lang.Class.privateGetMethodRecursive(Class.java:3048) at java.lang.Class.getMethod0(Class.java:3018) at java.lang.Class.getMethod(Class.java:1784) at sun.launcher.LauncherHelper.validateMainClass(LauncherHelper.java:544) at sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:526) Caused by: java.lang.ClassNotFoundException: javax.cache.configuration.Factory at java.net.URLClassLoader.findClass(URLClassLoader.java:381) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) ... 7 more [root@dbtestvm1 target]# [root@dbtestvm1 target]# [root@dbtestvm1 target]# [root@dbtestvm1 target]# [root@dbtestvm1 target]# echo $CLASSPATH /root/ignite/apache-ignite-fabric-1.6.0-bin/libs:/usr/java/default/jre/lib/ [root@dbtestvm1 target]# [root@dbtestvm1 target]# java -jar ignite-examples-1.6.0.jar org.apache.ignite.schema.Demo no main manifest attribute, in ignite-examples-1.6.0.jar [root@dbtestvm1 target]# [root@dbtestvm1 target]# == Regards Abhishek
Re: Automatic Persistence - POJOs and XMLs for couchbase
Thanks Andrey,Alexey and Val, The issue got resolved. The issue was with the enterprise version of couchbase 4.5.0. I removed it and installed the couchbase community version 4.1.0. And I am able to generate the pojos and xml files. I appreciate all of yours great efforts. Regards Abhishek On Tue, Sep 6, 2016 at 6:11 AM, Andrey Novikov wrote: > Hi, Abhishek Jain. > > I successfully connect to couchbase using Simba couchbase JDBC driver. > > For do this you need: > * create folder for driver jars in $IGNITE_HOME/libs (for example: > couchbase-driver) > * copy all jars from Driver folder in Simba_Couchbase_JDBC.zip > * copy SimbaCouchbaseJDBCDriver.lic > > I was able to load schemas, but loading table or view failed. Possible > problem in JDBC driver which is not have receiving metadata for tables. > > Can you please try to load table or view too? > > > > -- > View this message in context: http://apache-ignite-users.705 > 18.x6.nabble.com/Automatic-Persistence-POJOs-and-XMLs-for- > couchbase-tp7492p7546.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. >
Re: Automatic Persistence - POJOs and XMLs for couchbase
Thanks Val for replying soon. I will check with couchbase. As per their documentation, the license file should be in the same folder where the driver jar file is saved and I did so but of no help. Regards Abhishek On Fri, Sep 2, 2016 at 6:53 PM, vkulichenko wrote: > Hi, > > It looks like the misuse of Couchbase - the driver can't connect to the > server due to a licensing issue. You should refer to Couchbase docs and > figure out where the license file should be located. I'm unfortunately not > an expert, so can't help more. > > -Val > > > > -- > View this message in context: http://apache-ignite-users.705 > 18.x6.nabble.com/Automatic-Persistence-POJOs-and-XMLs-for- > couchbase-tp7492p7494.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. >
Automatic Persistence - POJOs and XMLs for couchbase
Hi, If somebody worked with Automatic Persistence for POJOs and XMLs creation for couchbase, please let me know the procedure for the same. (Although I have been successfully able to create the POJOs and XMLs for H2 database as mentioned in the Automatic Persistence section) I am getting the following error, though I have copied the simba license in the classpath also. [image: Inline image 1] Regards Abhishek
Re: Stored Procedure
Thankyou Val for your very quick response. Regards Abhishek -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Stored-Procedure-tp6548p6554.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Stored Procedure
Hi, I understand the stored procedures are NOT supported in apache ignite. Please let me know if I missed out something. Also, is there any SQL CLI/shell available for Apache ignite? Regards Abhishek -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Stored-Procedure-tp6548.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: REST API : Failed to find mandatory parameter in request: key
Thanks Val. Thanks for your quick response. Regards Abhishek -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/REST-API-Failed-to-find-mandatory-parameter-in-request-key-tp6430p6471.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: REST API : Failed to find mandatory parameter in request: key
Hi Guys, Please let me know if anybody knows about this error. Abhishek -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/REST-API-Failed-to-find-mandatory-parameter-in-request-key-tp6430p6445.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
