Azure Integration

[arthi]

Hi Team,

Can a Ignite grid run on Azure cloud?

Thanks,
Arthi



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Azure-Integration-tp4531.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: how to loadCache from Hbase

[vkulichenko]

Hi,

There is no example particularly for HBase, but it's no different from other
implementations - you need to implement CacheStore interface and provide it
in configuration.

I would start with extending convenient CacheStoreAdapter class and
implementing load/write/delete methods, like shown here:
https://apacheignite.readme.io/docs/persistent-store#cachestore-example

-Val



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/how-to-loadCache-from-Hbase-tp4528p4530.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Thanks for contributing IGNITE-3015 Fix GridGain references in Javadoc

[Alexey Kuznetsov]

I want to thank Matt Hoffman from the community side for the contribution
he has done in javadocs cleanup.

Look forward for new contributions from your side!

-- 
Alexey Kuznetsov
GridGain Systems
www.gridgain.com

how to loadCache from Hbase

[ght230]

Is there any example about using CacheStore.loadCache() to loading data from
Hbase?



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/how-to-loadCache-from-Hbase-tp4528.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Thanks for contributing IGNITE-3035 Postgres mssql JDBC discovery fix

[Alexey Kuznetsov]

I would like to thanks to

I want to thank Peter Griffiths from the community side for the
contribution he has done in JDBC discovery.

Look forward for new contributions from your side!

-- 
Alexey Kuznetsov
GridGain Systems
www.gridgain.com

Re: ignite logging not captured in log file (log4j)

[vkulichenko]

Can you clarify how exactly you're going to use rolling restart?

-Val



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/ignite-logging-not-captured-in-log-file-log4j-tp4334p4526.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: ignite logging not captured in log file (log4j)

[vkulichenko]

--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/ignite-logging-not-captured-in-log-file-log4j-tp4334p4525.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Client fails to connect - joinTimeout vs networkTimeout

[vkulichenko]

Hi,

You can limit the size of the allocated off heap memory for a cache by
setting CacheConfiguration.offHeapMaxMemory property. If it's exceeded,
entries will start to evict from cache on LRU basis. If you have a
persistence store, it will then loaded from from there. Otherwise, you lose
the data.

Refer to this documentation chapter for some performance and tuning tips:
https://apacheignite.readme.io/docs/preparing-for-production

-Val



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Client-fails-to-connect-joinTimeout-vs-networkTimeout-tp4419p4524.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: java.lang.OutOfMemoryError in normal Ignite usage

[Dmitriy Setrakyan]

1GB of heap is generally very small. The memory issue may or may not be
related to Ignite. I would suggest increasing the heap size and check the
heap graphs in any profiler, to make sure that it is not constantly growing
without being reclaimed. If it is, then I would check which objects are the
culprit - profiler provides this information.

On Mon, Apr 25, 2016 at 4:20 AM, Vladimir Ozerov 
wrote:

> Hi,
>
> Most probably, you just have insufficient heap, as queries require some
> heap space during execution. Probably you should give your node more heap
> and monitor it for some. If all is fine, you will see a saw-like pattern -
> when memory is allocated and then release. If there is a leak, you will see
> constant heap growth.
>
> Vladimir.
>
> On Sun, Apr 24, 2016 at 1:53 AM, Eduardo Julian 
> wrote:
>
>> Hi, everyone.
>>
>> I started a program 3 days ago on a server with 1GB RAM.
>>
>> Everything was running smoothly until a couple of hours ago, when the
>> service wasn't responding.
>> When we go check the logs, there is an OOMError with an Ignite
>> stack-trace tagging along.
>>
>> All that I store on that server is stored on Ignite (with read-through
>> and write-through to a MySQL DB).
>> It's fairly light stuff, just some objects with 10+ fields, and it's just
>> 1 cache right now.
>>
>> However, in the logs, the bulk of the operations preceding the OOM error
>> were read-operations that neither created nor updated the data on Ignite.
>> Just performed some queries.
>>
>> And yet, for some reason, there was a HashMap being updated somewhere,
>> which triggered the OOM error.
>>
>> Check it out:
>>
>> Apr 23, 2016 4:35:44 PM org.apache.ignite.logger.java.JavaLogger error
>> SEVERE: Caught unhandled exception in NIO worker thread (restart the
>> node).
>> java.lang.OutOfMemoryError: Java heap space
>> at java.util.HashMap$KeySet.iterator(HashMap.java:912)
>> at java.util.HashSet.iterator(HashSet.java:172)
>> at
>> java.util.Collections$UnmodifiableCollection$1.(Collections.java:1039)
>> at
>> java.util.Collections$UnmodifiableCollection.iterator(Collections.java:1038)
>> at
>> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.checkIdle(GridNioServer.java:1489)
>> at
>> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:1406)
>> at
>> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1280)
>> at
>> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
>> at java.lang.Thread.run(Thread.java:745)
>>
>> Apr 23, 2016 4:35:45 PM org.apache.ignite.logger.java.JavaLogger error
>> SEVERE: Runtime error caught during grid runnable execution: GridWorker
>> [name=grid-nio-worker-0, gridName=null, finished=false, isCancelled=false,
>> hashCode=1645791145, interrupted=false, runner=grid-nio-worker-0-#40%null%]
>> java.lang.OutOfMemoryError: Java heap space
>> at java.util.HashMap$KeySet.iterator(HashMap.java:912)
>> at java.util.HashSet.iterator(HashSet.java:172)
>> at
>> java.util.Collections$UnmodifiableCollection$1.(Collections.java:1039)
>> at
>> java.util.Collections$UnmodifiableCollection.iterator(Collections.java:1038)
>> at
>> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.checkIdle(GridNioServer.java:1489)
>> at
>> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:1406)
>> at
>> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1280)
>> at
>> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
>> at java.lang.Thread.run(Thread.java:745)
>>
>> Apr 23, 2016 4:35:46 PM org.apache.ignite.logger.java.JavaLogger error
>> SEVERE: Runtime error caught during grid runnable execution: GridWorker
>> [name=partition-exchanger, gridName=null, finished=false,
>> isCancelled=false, hashCode=685490869, interrupted=false,
>> runner=exchange-worker-#45%null%]
>> java.lang.OutOfMemoryError: Java heap space
>> at java.util.HashMap.newNode(HashMap.java:1734)
>> at java.util.HashMap.putVal(HashMap.java:630)
>> at java.util.HashMap.put(HashMap.java:611)
>> at
>> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionMap2.put(GridDhtPartitionMap2.java:112)
>> at
>> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionMap2.(GridDhtPartitionMap2.java:96)
>> at
>> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionFullMap.(GridDhtPartitionFullMap.java:107)
>> at
>> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.partitionMap(GridDhtPartitionTopologyImpl.java:841)
>> at
>> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.sendAllPartitions(GridCachePartitionExchangeManager.java:747)
>> at
>> 

Cluster Stopped when no activity for hours

[arthi]

Hi Team,

I have a ignite cluster with 11 nodes, and I have four partitioned caches
all using off heap memory.
I want to load several GBs of data into the caches (each node is 256GB RAM).
I use loadCache API to load, and it takes a lot of time to load the data
into cache.

I leave the cluster as is at night (my timeout!), and try to log in the next
day, all the nodes are stopped!

I only see these in the work logs, and was not sure if this is a setting
issue or something -
[20:06:43,854][INFO ][Thread-2][G] Invoking shutdown hook...
[20:06:43,860][INFO ][Thread-2][GridTcpRestProtocol] Command protocol
successfully stopped: TCP binary
[20:06:46,462][INFO ][Thread-2][GridCacheProcessor] Stopped cache:
ignite-marshaller-sys-cache
[20:06:46,462][INFO ][Thread-2][GridCacheProcessor] Stopped cache:
ignite-sys-cache
[20:06:46,463][INFO ][Thread-2][GridCacheProcessor] Stopped cache:
ignite-atomics-sys-cache
[20:06:46,463][INFO ][Thread-2][GridCacheProcessor] Stopped cache:
TOP_SHOP_DATA_CACHE
[20:06:46,463][INFO ][Thread-2][GridCacheProcessor] Stopped cache:
PROD_HIER_CACHE
[20:06:46,463][INFO ][Thread-2][GridCacheProcessor] Stopped cache:
MARKET_POD_ACV_CACHE
[20:06:46,464][INFO ][Thread-2][GridCacheProcessor] Stopped cache:
SHOP_ITEM_BITMAP_CACHE
[20:06:46,757][INFO ][Thread-2][IgniteKernal%cip]

>>> +---+
>>> Ignite ver.
>>> 1.5.0-final#20151229-sha1:f1f8cda2f3f62231f42a59951bf34c39577c1bec
>>> stopped OK
>>> +---+
>>> Grid name: cip
>>> Grid uptime: 07:32:12:877

Here is my config file -
cip-ignite-client.xml

  

Thanks,
Arthi




--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Cluster-Stopped-when-no-activity-for-hours-tp4519.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: IgniteSemaphore problem

[Dmitriy Setrakyan]

Here is a link to the nightly builds:
https://cwiki.apache.org/confluence/display/IGNITE/Nightly+Builds

On Mon, Apr 25, 2016 at 4:36 AM, Vladimir Ozerov 
wrote:

> Hi,
>
> There was several issues associated with distributed semaphore in 1.5.0
> release. As far as I know most of the will be fixed in 1.6.0 release.
> Can you try building from current development master and see if the
> problem is still there?
>
> Vladimir.
>
> On Wed, Apr 20, 2016 at 1:00 PM, swoky  wrote:
>
>> now we have two nodes,
>> created an IgniteSemaphore  in node A ,then we can use it in node B,
>>
>> but when node A down ,can't use it in node B any more,
>>
>> is there some Configurations i missed?
>>
>> below is my Configuration file
>>
>> -
>> http://www.springframework.org/schema/beans;
>>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>>xmlns:util="http://www.springframework.org/schema/util;
>>xsi:schemaLocation="
>> http://www.springframework.org/schema/beans
>> http://www.springframework.org/schema/beans/spring-beans.xsd
>> http://www.springframework.org/schema/util
>> http://www.springframework.org/schema/util/spring-util.xsd;>
>>
>> 
>>
>> 
>> > class="org.apache.ignite.configuration.CacheConfiguration">
>>
>> 
>>
>> 
>> 
>> 
>>
>>
>> 
>> > class="org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi">
>> 
>> >
>> class="org.apache.ignite.spi.discovery.tcp.ipfinder.zk.TcpDiscoveryZookeeperIpFinder">
>> > value="false" />
>> > value="127.0.0.1:2181"/>
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> and the java code :
>> ---
>> Ignite ignite = Ignition.start("d:\x\ignite.xml");
>>
>> IgniteSemaphore semaphore = ignite.semaphore("semName",
>> // Distributed
>> semaphore name.
>> 90, // Number of permits.
>> true, // Release acquired permits if
>> node, that owned them, left
>> topology.
>> true // Create if it doesn't exist.
>> );
>> -
>>
>>
>>
>> --
>> View this message in context:
>> http://apache-ignite-users.70518.x6.nabble.com/IgniteSemaphore-problem-tp4366.html
>> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>>
>
>

Re: Exception while using primary key with “underscore” character in apache ignite

[Alexey Kuznetsov]

There were a lot of bugs fixed in Schema Import Utility recently.
Could you try to re-generate POJOs and configs one more time using Schema
Import Utility from latest [nightly build][1]?


  [1]:
https://builds.apache.org/view/H-L/view/Ignite/job/Ignite-nightly/lastSuccessfulBuild/

On Tue, Apr 26, 2016 at 5:36 AM, vkulichenko 
wrote:

> Hi,
>
> Can you please properly subscribe to the mailing list so that the community
> can receive email notifications? Here is the instruction:
>
> http://apache-ignite-users.70518.x6.nabble.com/mailing_list/MailingListOptions.jtp?forum=1
>
>
> anishdevasia wrote
> > Following exception occurs when using apache ignite data grid with schema
> > import utility. A table "employee" created with primary key "emp_no" as
> > the column name. generated pojo classes and configuration using apache
> > ignite schema import utility. tried executing example program that comes
> > with distribution. Following it the exception. apache ignite version is :
> > 1.5.0-final
> > It seems like if the table is having any index that has columns with "_"
> > character is causing this issue.
> >
> >
> [16:45:58,890][ERROR][exchange-worker-#49%null%][GridDhtPartitionsExchangeFuture]
> > Failed to reinitialize local partitions (preloading will be stopped):
> > GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion [topVer=1,
> > minorTopVer=1], nodeId=1073ac4a, evt=DISCOVERY_CUSTOM_EVT]
> > class org.apache.ignite.IgniteCheckedException: Failed to register query
> > type: TypeDescriptor [name=Employees, fields={empNo=class
> > java.lang.Object, birthDate=class java.sql.Date, firstName=class
> > java.lang.Object, lastName=class java.lang.Object, gender=class
> > java.lang.Object, hireDate=class java.sql.Date},
> > indexes={PRIMARY=IndexDescriptor [type=SORTED]}, fullTextIdx=null,
> > keyCls=class java.lang.Object, valCls=class java.lang.Object,
> > valTextIdx=false, registered=false]
> > at
> >
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.registerType(IgniteH2Indexing.java:1167)
> > at
> >
> org.apache.ignite.internal.processors.query.GridQueryProcessor.initializeCache(GridQueryProcessor.java:291)
> > at
> >
> org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStart(GridQueryProcessor.java:457)
> > at
> >
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCache(GridCacheProcessor.java:1038)
> > at
> >
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:1648)
> > at
> >
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCachesStart(GridCacheProcessor.java:1563)
> > at
> >
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.startCaches(GridDhtPartitionsExchangeFuture.java:956)
> > at
> >
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:523)
> > at
> >
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:1297)
> > at
> >
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> > at java.lang.Thread.run(Thread.java:745)
> > Caused by: org.h2.jdbc.JdbcSQLException: Column "EMP_NO" not found; SQL
> > statement:
> > CREATE TABLE "EmployeesCache".Employees (_key OTHER NOT NULL,_val
> > OTHER,empNo OTHER,birthDate DATE,firstName OTHER,lastName OTHER,gender
> > OTHER,hireDate DATE) engine
> > "org.apache.ignite.internal.processors.query.h2.opt.GridH2Table$Engine"
> > [42122-175]
> > at
> > org.h2.message.DbException.getJdbcSQLException(DbException.java:332)
> > at org.h2.message.DbException.get(DbException.java:172)
> > at org.h2.message.DbException.get(DbException.java:149)
> > at org.h2.table.Table.getColumn(Table.java:626)
> > at
> >
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$TableDescriptor.createIndexes(IgniteH2Indexing.java:1984)
> > at org.apache.ignite.internal.processors.query.h2.opt.GridH2Table.
> > 
> > (GridH2Table.java:106)
> > at
> >
> org.apache.ignite.internal.processors.query.h2.opt.GridH2Table$Engine.createTable(GridH2Table.java:675)
> > at
> >
> org.apache.ignite.internal.processors.query.h2.opt.GridH2Table$Engine.createTable(GridH2Table.java:659)
> > at org.h2.schema.Schema.createTable(Schema.java:584)
> > at org.h2.command.ddl.CreateTable.update(CreateTable.java:135)
> > at org.h2.command.CommandContainer.update(CommandContainer.java:79)
> > at org.h2.command.Command.executeUpdate(Command.java:253)
> > at org.h2.jdbc.JdbcStatement.executeInternal(JdbcStatement.java:181)
> > at org.h2.jdbc.JdbcStatement.execute(JdbcStatement.java:156)
> > at
> >
> 

Re: Client fails to connect - joinTimeout vs networkTimeout

[bintisepaha]

Val, we are going to try 10 GB off heap storage with 4 GB heap sizes this
week and next and will revert how that looks. A follow up question - what
happens when data does not fit off heap and we have defined affinity, where
does it go - on heap or do we start seeing inconsistent results? We do not
have swap sapce configured yet or any eviction policy.

Another question I asked earlier was about if you guys had any specific GC
tuning recommendations? 



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Client-fails-to-connect-joinTimeout-vs-networkTimeout-tp4419p4516.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: ignite logging not captured in log file (log4j)

[bintisepaha]

I will give it one more shot on our end with several clients connected to the
grid when we attempt to restart and let you know if we saw the same effect.

Does ignite support a rolling restart methodology?



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/ignite-logging-not-captured-in-log-file-log4j-tp4334p4515.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Exception while using primary key with “underscore” character in apache ignite

[vkulichenko]

Hi,

Can you please properly subscribe to the mailing list so that the community
can receive email notifications? Here is the instruction:
http://apache-ignite-users.70518.x6.nabble.com/mailing_list/MailingListOptions.jtp?forum=1


anishdevasia wrote
> Following exception occurs when using apache ignite data grid with schema
> import utility. A table "employee" created with primary key "emp_no" as
> the column name. generated pojo classes and configuration using apache
> ignite schema import utility. tried executing example program that comes
> with distribution. Following it the exception. apache ignite version is :
> 1.5.0-final
> It seems like if the table is having any index that has columns with "_"
> character is causing this issue.
> 
> [16:45:58,890][ERROR][exchange-worker-#49%null%][GridDhtPartitionsExchangeFuture]
> Failed to reinitialize local partitions (preloading will be stopped):
> GridDhtPartitionExchangeId [topVer=AffinityTopologyVersion [topVer=1,
> minorTopVer=1], nodeId=1073ac4a, evt=DISCOVERY_CUSTOM_EVT]
> class org.apache.ignite.IgniteCheckedException: Failed to register query
> type: TypeDescriptor [name=Employees, fields={empNo=class
> java.lang.Object, birthDate=class java.sql.Date, firstName=class
> java.lang.Object, lastName=class java.lang.Object, gender=class
> java.lang.Object, hireDate=class java.sql.Date},
> indexes={PRIMARY=IndexDescriptor [type=SORTED]}, fullTextIdx=null,
> keyCls=class java.lang.Object, valCls=class java.lang.Object,
> valTextIdx=false, registered=false]
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.registerType(IgniteH2Indexing.java:1167)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.initializeCache(GridQueryProcessor.java:291)
> at
> org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStart(GridQueryProcessor.java:457)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCache(GridCacheProcessor.java:1038)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:1648)
> at
> org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCachesStart(GridCacheProcessor.java:1563)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.startCaches(GridDhtPartitionsExchangeFuture.java:956)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:523)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:1297)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: org.h2.jdbc.JdbcSQLException: Column "EMP_NO" not found; SQL
> statement:
> CREATE TABLE "EmployeesCache".Employees (_key OTHER NOT NULL,_val
> OTHER,empNo OTHER,birthDate DATE,firstName OTHER,lastName OTHER,gender
> OTHER,hireDate DATE) engine
> "org.apache.ignite.internal.processors.query.h2.opt.GridH2Table$Engine"
> [42122-175]
> at
> org.h2.message.DbException.getJdbcSQLException(DbException.java:332)
> at org.h2.message.DbException.get(DbException.java:172)
> at org.h2.message.DbException.get(DbException.java:149)
> at org.h2.table.Table.getColumn(Table.java:626)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$TableDescriptor.createIndexes(IgniteH2Indexing.java:1984)
> at org.apache.ignite.internal.processors.query.h2.opt.GridH2Table.
> 
> (GridH2Table.java:106)
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2Table$Engine.createTable(GridH2Table.java:675)
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2Table$Engine.createTable(GridH2Table.java:659)
> at org.h2.schema.Schema.createTable(Schema.java:584)
> at org.h2.command.ddl.CreateTable.update(CreateTable.java:135)
> at org.h2.command.CommandContainer.update(CommandContainer.java:79)
> at org.h2.command.Command.executeUpdate(Command.java:253)
> at org.h2.jdbc.JdbcStatement.executeInternal(JdbcStatement.java:181)
> at org.h2.jdbc.JdbcStatement.execute(JdbcStatement.java:156)
> at
> org.apache.ignite.internal.processors.query.h2.opt.GridH2Table$Engine.createTable(GridH2Table.java:700)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.createTable(IgniteH2Indexing.java:1288)
> at
> org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.registerType(IgniteH2Indexing.java:1160)
> ... 10 more
> [16:45:58,890][ERROR][exchange-worker-#49%null%][GridCachePartitionExchangeManager]
> Runtime error caught during grid runnable execution: GridWorker
> [name=partition-exchanger, gridName=null, finished=false,
> isCancelled=false, hashCode=2115830072, interrupted=false,
> 

Re: Can't load log handler "org.apache.ignite.logger.java.JavaLoggerFileHandler"

[vkulichenko]

Hi,

Can you please properly subscribe to the mailing list so that the community
can receive email notifications? Here is the instruction:
http://apache-ignite-users.70518.x6.nabble.com/mailing_list/MailingListOptions.jtp?forum=1


suhuadong wrote
> My project based spring boot and ignite(1.5.0.final)
> I pack my projcet to XXX.jar by mvn.
> I'm trying to run the jar,but I'm having a strange ClassNotFoundException.
> 
> Here is full stack trace:

 
This is a known issue with Java logger being used within an application
server. I would recommend to switch to Log4J instead. To do this, you should
include 'ignite-log4j' dependency and Log4J logging for Ignite will be
enabled automatically.

-Val



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Can-t-load-log-handler-org-apache-ignite-logger-java-JavaLoggerFileHandler-tp4490p4513.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Error running nodes in .net and c++

[Murthy Kakarlamudi]

Hi Alexey...Apologize the delay in my response. Below are the 2 links from
gdrive for my Java and c++ projects.

Java Project:
https://drive.google.com/open?id=0B8lM91-_3MwRZmF6N0tnN1pyN2M

C++ Project:
https://drive.google.com/open?id=0B8lM91-_3MwRMGE5akVWVXc0RXc

Please let me know if you have any difficulty downloading the projects.

Thanks,
Satya.

On Mon, Apr 25, 2016 at 10:49 AM, Alexey Kuznetsov 
wrote:

> I see in stack trace "Caused by: class org.apache.ignite.IgniteException:
> Spring application context resource is not injected."
>
> Also CacheJdbcPojoStoreFactory contains such declaration:
> @SpringApplicationContextResource
> private transient Object appCtx;
>
> Anybody know why appCtx may not be injected?
>
> Also Satya, it is possible for you to prepare small reproducible example
> that we could debug?
>
>
> On Mon, Apr 25, 2016 at 9:39 PM, Vladimir Ozerov 
> wrote:
>
>> Alexey Kuznetsov,
>>
>> Provided you have more expertise with POJO store, could you please advise
>> what could cause this exception? Seems that POJO store expects some
>> injection, which doesn't happen.
>> Are there any specific requirements here? C++ node starts as a regular
>> node and also use Spring.
>>
>> Vladimir.
>>
>> On Mon, Apr 25, 2016 at 5:32 PM, Murthy Kakarlamudi 
>> wrote:
>>
>>> Any help on this issue please...
>>>
>>> On Sat, Apr 16, 2016 at 7:29 PM, Murthy Kakarlamudi 
>>> wrote:
>>>
 Hi,
In my use case, I am starting a node from .net which loads data from
 SQL Server table into cache upon start up. I have to read those entries
 from cache from a c++ node that acts as a client. I am getting the below
 error trying to start the node from c++.

 [19:08:57] Security status [authentication=off, tls/ssl=off]
 [19:08:58,163][SEVERE][main][IgniteKernal] Failed to start manager:
 GridManagerAdapter [enabled=true,
 name=o.a.i.i.managers.discovery.GridDiscoveryManager]
 class org.apache.ignite.IgniteCheckedException: Remote node has peer
 class loading enabled flag different from local [locId8=f02445af,
 locPeerClassLoading=true, rmtId8=8e52f9c9, rmtPeerClassLoading=false,
 rmtAddrs=[LAPTOP-QIT4AVOG/0:0:0:0:0:0:0:1, LAPTOP-QIT4AVOG/127.0.0.1,
 LAPTOP-QIT4AVOG/192.168.0.5,
 LAPTOP-QIT4AVOG/2001:0:9d38:90d7:145b:5bf:bb9b:11d9,
 LAPTOP-QIT4AVOG/2600:8806:0:8d00:0:0:0:1,
 /2600:8806:0:8d00:3ccf:1e94:1ab4:83a9,
 /2600:8806:0:8d00:f114:bf30:2068:352d]]
 at
 org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.checkAttributes(GridDiscoveryManager.java:1027)
 at
 org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.start(GridDiscoveryManager.java:680)
 at
 org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1505)
 at
 org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:917)
 at
 org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1688)
 at
 org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1547)
 at
 org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1003)
 at
 org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:534)
 at
 org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:515)
 at org.apache.ignite.Ignition.start(Ignition.java:322)
 at
 org.apache.ignite.internal.processors.platform.PlatformAbstractBootstrap.start(PlatformAbstractBootstrap.java

 Below if my config for .net node:
 

 http://www.springframework.org/schema/beans;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="
 http://www.springframework.org/schema/beans
 http://www.springframework.org/schema/beans/spring-beans.xsd;>
   >>> class="org.apache.ignite.configuration.IgniteConfiguration">
 
   >>> class="org.apache.ignite.configuration.ConnectorConfiguration">
 
   
 

 
   
 >>> class="org.apache.ignite.configuration.CacheConfiguration">
   
   
   
   
   
   
 >>> class="org.apache.ignite.platform.dotnet.PlatformDotNetCacheStoreFactory">
   >>> value="TestIgniteDAL.SQLServerStore, TestIgniteDAL"/>
 
   
   
 
   
 
 
 
 
   
 
 
 
 
 >>> value="java.lang.Integer"/>
 
   
   

Re: Which is a better choice,Ignite client Node or Memcached client?

[vkulichenko]

Hi,

Can you please properly subscribe to the mailing list so that the community
can receive email notifications? Here is the instruction:
http://apache-ignite-users.70518.x6.nabble.com/mailing_list/MailingListOptions.jtp?forum=1


suhuadong wrote
> When i readed ignite documents,  i know that access cache by Inite client
> Node or Memcached client.
>   I think  that Memcached client more  light weight than Memcached
> client,but way of Memcached client has more functions.
>   which is a better choice,Ignite client Node  or Memcached client?

Generally, using the Ignite client node is the recommended way. It will give
you all the available APIs and much better performance. I would use
Memcached protocol only if your application already depends on it and
changing the code is not an option.

-Val



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Which-is-a-better-choice-Ignite-client-Node-or-Memcached-client-tp4488p4511.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Performance Issue - Threads blocking

[vkulichenko]

Matt Hoffman wrote
> Do you think that would be a candidate for the "Performance tips" page in
> the docs? I know I've referred to that page a few times recently myself.

That's a good point, thanks. I updated the docs.

-Val



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Performance-Issue-Threads-blocking-tp4433p4509.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Performance Issue - Threads blocking

[vkulichenko]

Hi Matt,


Matt Hoffman wrote
> Based on his claim of a lot of threads waiting on the same locks, I
> assumed
> that's what was happening -- high contention for a few cache keys. I don't
> know his use case, but I can imagine cases with a fairly small number of
> very "hot" entries.
> It wouldn't necessarily require very few keys, right? Just high contention
> on a few of them.

This is right, but what are you expectations in this scenario? Concurrent
updates/reads of the same entry have to be synchronized, and Ignite locks
only on per-entry level. In my view, this is the highest concurrency level
possible.





--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Performance-Issue-Threads-blocking-tp4433p4508.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Ignite Installation with Spark under CDH

[mdolgonos]

Vladimir,
There are 2 things that I'm experiencing so far:
1. I have added the following code to spark-env.sh in my CDH installation
IGNITE_HOME=/etc/ignite-1.5.0
IGNITE_LIBS="${IGNITE_HOME}/libs/*"

for file in ${IGNITE_HOME}/libs/*
do
if [ -d ${file} ] && [ "${file}" != "${IGNITE_HOME}"/libs/optional ];
then
IGNITE_LIBS=${IGNITE_LIBS}:${file}/*
fi
done

but Ignite jars are still not recognized by Spark after restarting Spark as
well as the entire CDH
. My location of CDH is the default one:
/opt/cloudera/parcels/CDH-5.5.2-1.cdh5.5.2.p0.4/etc/spark/conf.dist
So I decided to compile my code into a jar-with-dependencies which led me to
the second issue:

2. Looks like the jars were discovered by spark-submit, however, now I'm
getting the following exception:
Exception in thread "main" java.lang.NoClassDefFoundError:
javax/cache/configuration/MutableConfiguration
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:800)
at
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:449)
at java.net.URLClassLoader.access$100(URLClassLoader.java:71)
at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.marshallerSystemCache(IgnitionEx.java:2098)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.initializeDefaultCacheConfiguration(IgnitionEx.java:1914)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.initializeConfiguration(IgnitionEx.java:1899)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1573)
at
org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1547)
at
org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1003)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:534)
at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:515)
at org.apache.ignite.Ignition.start(Ignition.java:322)
at
org.apache.ignite.spark.IgniteContext.ignite(IgniteContext.scala:153)
at
org.apache.ignite.spark.IgniteContext.(IgniteContext.scala:62)
at
training.PnLMergerVectorIgnite$.main(PnLMergerVectorIgnite.scala:50)
at training.PnLMergerVectorIgnite.main(PnLMergerVectorIgnite.scala)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.apache.spark.deploy.SparkSubmit$.org$apache$spark$deploy$SparkSubmit$$runMain(SparkSubmit.scala:672)
at
org.apache.spark.deploy.SparkSubmit$.doRunMain$1(SparkSubmit.scala:180)
at
org.apache.spark.deploy.SparkSubmit$.submit(SparkSubmit.scala:205)
at org.apache.spark.deploy.SparkSubmit$.main(SparkSubmit.scala:120)
at org.apache.spark.deploy.SparkSubmit.main(SparkSubmit.scala)
Caused by: java.lang.ClassNotFoundException:
javax.cache.configuration.MutableConfiguration
at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
I know that the class javax.cache.configuration.MutableConfiguration belongs
to cache-api-1.0.0.jar and I see it present in my jar-with-dependencies

Thank you for looking at this.




--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Ignite-Installation-with-Spark-under-CDH-tp4457p4507.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Problems About Loadcache Streamer And Putall

[Dmitriy Setrakyan]

DataStreamer allows to inject high volume of data into Ignite from a
client. It essentially is an equivalent of a bulk-put operation which
automatically batches the data on the client side before sending it to
servers.

loadCache() method, on the other hand, will load data from the underlying
store. It will be executed on each of the server nodes, which in turn will
connect to the database to load their portion of the data.

Here is a link to more documentation:
https://apacheignite.readme.io/docs/data-loading

D.

On Mon, Apr 25, 2016 at 7:18 AM, Level D <724172...@qq.com> wrote:

> Hi，
>
> I've already read the development manul about these three methods. And it
> says that putall is inefficient when cluster loads a large nember of data.
>
> Here comes my problems.
>
> What are the advantages of localcache and streamer in big data?
> Are there any mesures to ensure data is not lost? Like at least once or
> only once...
>
>

Re: ignite logging not captured in log file (log4j)

[bintisepaha]

After enabling the dependency this is what I used. Does not seem to log
anything extra than my java code in the log file. 

log4j.logger.org.apache.ignite=ERROR
log4j.logger.org.apache.activemq=INFO
log4j.logger.org.apache.commons=INFO



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/ignite-logging-not-captured-in-log-file-log4j-tp4334p4505.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Error running nodes in .net and c++

[Alexey Kuznetsov]

I see in stack trace "Caused by: class org.apache.ignite.IgniteException:
Spring application context resource is not injected."

Also CacheJdbcPojoStoreFactory contains such declaration:
@SpringApplicationContextResource
private transient Object appCtx;

Anybody know why appCtx may not be injected?

Also Satya, it is possible for you to prepare small reproducible example
that we could debug?


On Mon, Apr 25, 2016 at 9:39 PM, Vladimir Ozerov 
wrote:

> Alexey Kuznetsov,
>
> Provided you have more expertise with POJO store, could you please advise
> what could cause this exception? Seems that POJO store expects some
> injection, which doesn't happen.
> Are there any specific requirements here? C++ node starts as a regular
> node and also use Spring.
>
> Vladimir.
>
> On Mon, Apr 25, 2016 at 5:32 PM, Murthy Kakarlamudi 
> wrote:
>
>> Any help on this issue please...
>>
>> On Sat, Apr 16, 2016 at 7:29 PM, Murthy Kakarlamudi 
>> wrote:
>>
>>> Hi,
>>>In my use case, I am starting a node from .net which loads data from
>>> SQL Server table into cache upon start up. I have to read those entries
>>> from cache from a c++ node that acts as a client. I am getting the below
>>> error trying to start the node from c++.
>>>
>>> [19:08:57] Security status [authentication=off, tls/ssl=off]
>>> [19:08:58,163][SEVERE][main][IgniteKernal] Failed to start manager:
>>> GridManagerAdapter [enabled=true,
>>> name=o.a.i.i.managers.discovery.GridDiscoveryManager]
>>> class org.apache.ignite.IgniteCheckedException: Remote node has peer
>>> class loading enabled flag different from local [locId8=f02445af,
>>> locPeerClassLoading=true, rmtId8=8e52f9c9, rmtPeerClassLoading=false,
>>> rmtAddrs=[LAPTOP-QIT4AVOG/0:0:0:0:0:0:0:1, LAPTOP-QIT4AVOG/127.0.0.1,
>>> LAPTOP-QIT4AVOG/192.168.0.5,
>>> LAPTOP-QIT4AVOG/2001:0:9d38:90d7:145b:5bf:bb9b:11d9,
>>> LAPTOP-QIT4AVOG/2600:8806:0:8d00:0:0:0:1,
>>> /2600:8806:0:8d00:3ccf:1e94:1ab4:83a9,
>>> /2600:8806:0:8d00:f114:bf30:2068:352d]]
>>> at
>>> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.checkAttributes(GridDiscoveryManager.java:1027)
>>> at
>>> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.start(GridDiscoveryManager.java:680)
>>> at
>>> org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1505)
>>> at
>>> org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:917)
>>> at
>>> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1688)
>>> at
>>> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1547)
>>> at
>>> org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1003)
>>> at
>>> org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:534)
>>> at
>>> org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:515)
>>> at org.apache.ignite.Ignition.start(Ignition.java:322)
>>> at
>>> org.apache.ignite.internal.processors.platform.PlatformAbstractBootstrap.start(PlatformAbstractBootstrap.java
>>>
>>> Below if my config for .net node:
>>> 
>>>
>>> http://www.springframework.org/schema/beans;
>>>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>>>xsi:schemaLocation="
>>> http://www.springframework.org/schema/beans
>>> http://www.springframework.org/schema/beans/spring-beans.xsd;>
>>>   >> class="org.apache.ignite.configuration.IgniteConfiguration">
>>> 
>>>   >> class="org.apache.ignite.configuration.ConnectorConfiguration">
>>> 
>>>   
>>> 
>>>
>>> 
>>>   
>>> 
>>>   
>>>   
>>>   
>>>   
>>>   
>>>   
>>> >> class="org.apache.ignite.platform.dotnet.PlatformDotNetCacheStoreFactory">
>>>   >> value="TestIgniteDAL.SQLServerStore, TestIgniteDAL"/>
>>> 
>>>   
>>>   
>>> 
>>>   
>>> 
>>> 
>>> 
>>> 
>>>   
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>>   
>>> 
>>> 
>>> 
>>>   
>>> 
>>>   
>>> 
>>>   
>>> 
>>>   
>>> 
>>>   
>>> 
>>>
>>> 
>>>   >> class="org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi">
>>> 
>>>   
>>> 
>>>
>>> 
>>>   
>>> 
>>>   >> class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder">
>>> 
>>>   
>>> 127.0.0.1:47500..47509
>>>   
>>> 
>>>   
>>> 
>>>   
>>> 
>>>   
>>> 
>>>

Re: Not able to save data in Ignite datagrid using JavaIgniteRDD

[Vladimir Ozerov]

Hi Vij,

I am a bit confused - do you still have any problems? Because one message
earlier you mentioned that finally it worked. Is any assistance still
needed?

Vladimir.

On Thu, Apr 21, 2016 at 7:32 AM, vijayendra bhati 
wrote:

> Hi Alexei,
>
> Here it is, the file StockSimulationsCacheWriter (2).java is the one
> which is not working.
>
> Regards,
> Vij
>
>
> On Thursday, April 21, 2016 1:54 AM, Alexei Scherbakov <
> alexey.scherbak...@gmail.com> wrote:
>
>
> Hi,
>
> It's very strange, because JavaIgniteContext is just a wrapper around
> IgniteContext.
> Could you provide the source code describing your problem ?
>
> 2016-04-20 21:14 GMT+03:00 vijayendra bhati :
>
> Its working now.I moved from JavaIgniteContext to IgniteContext.
> Also invoked igniteConext.fromCache(cacheConfiguration) rather than java
> igniteConext.fromCache(cacheName)
>
> Also while initializing cacheConfiguration , added index to it.
>
> Thanks,
> Vij
>
>
> On Wednesday, April 20, 2016 11:17 PM, vijayendra bhati <
> veejayend...@yahoo.com> wrote:
>
>
> Hi,
> I am trying to save data in Ignite datagrid using JavaIgniteRDD by calling
> method savePairs().
> Some how job is getting finished properly , am not getting any
> exception.Still there is not data in cache.I am checking through H2 debug
> console.
>
> I am not ablel to understand what could be the reason.The other thing is
> how to specify Indexes when using JavaIgniteContext.
>
> Regards,
> Vij
>
>
>
>
>
> --
>
> Best regards,
> Alexei Scherbakov
>
>
>

Re: Error running nodes in .net and c++

[Vladimir Ozerov]

Alexey Kuznetsov,

Provided you have more expertise with POJO store, could you please advise
what could cause this exception? Seems that POJO store expects some
injection, which doesn't happen.
Are there any specific requirements here? C++ node starts as a regular node
and also use Spring.

Vladimir.

On Mon, Apr 25, 2016 at 5:32 PM, Murthy Kakarlamudi 
wrote:

> Any help on this issue please...
>
> On Sat, Apr 16, 2016 at 7:29 PM, Murthy Kakarlamudi 
> wrote:
>
>> Hi,
>>In my use case, I am starting a node from .net which loads data from
>> SQL Server table into cache upon start up. I have to read those entries
>> from cache from a c++ node that acts as a client. I am getting the below
>> error trying to start the node from c++.
>>
>> [19:08:57] Security status [authentication=off, tls/ssl=off]
>> [19:08:58,163][SEVERE][main][IgniteKernal] Failed to start manager:
>> GridManagerAdapter [enabled=true,
>> name=o.a.i.i.managers.discovery.GridDiscoveryManager]
>> class org.apache.ignite.IgniteCheckedException: Remote node has peer
>> class loading enabled flag different from local [locId8=f02445af,
>> locPeerClassLoading=true, rmtId8=8e52f9c9, rmtPeerClassLoading=false,
>> rmtAddrs=[LAPTOP-QIT4AVOG/0:0:0:0:0:0:0:1, LAPTOP-QIT4AVOG/127.0.0.1,
>> LAPTOP-QIT4AVOG/192.168.0.5,
>> LAPTOP-QIT4AVOG/2001:0:9d38:90d7:145b:5bf:bb9b:11d9,
>> LAPTOP-QIT4AVOG/2600:8806:0:8d00:0:0:0:1,
>> /2600:8806:0:8d00:3ccf:1e94:1ab4:83a9,
>> /2600:8806:0:8d00:f114:bf30:2068:352d]]
>> at
>> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.checkAttributes(GridDiscoveryManager.java:1027)
>> at
>> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.start(GridDiscoveryManager.java:680)
>> at
>> org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1505)
>> at
>> org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:917)
>> at
>> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1688)
>> at
>> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1547)
>> at
>> org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1003)
>> at
>> org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:534)
>> at
>> org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:515)
>> at org.apache.ignite.Ignition.start(Ignition.java:322)
>> at
>> org.apache.ignite.internal.processors.platform.PlatformAbstractBootstrap.start(PlatformAbstractBootstrap.java
>>
>> Below if my config for .net node:
>> 
>>
>> http://www.springframework.org/schema/beans;
>>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>>xsi:schemaLocation="
>> http://www.springframework.org/schema/beans
>> http://www.springframework.org/schema/beans/spring-beans.xsd;>
>>   > class="org.apache.ignite.configuration.IgniteConfiguration">
>> 
>>   > class="org.apache.ignite.configuration.ConnectorConfiguration">
>> 
>>   
>> 
>>
>> 
>>   
>> 
>>   
>>   
>>   
>>   
>>   
>>   
>> > class="org.apache.ignite.platform.dotnet.PlatformDotNetCacheStoreFactory">
>>   > value="TestIgniteDAL.SQLServerStore, TestIgniteDAL"/>
>> 
>>   
>>   
>> 
>>   
>> 
>> 
>> 
>> 
>>   
>> 
>> 
>> 
>> 
>> 
>> 
>>   
>> 
>> 
>> 
>>   
>> 
>>   
>> 
>>   
>> 
>>   
>> 
>>   
>> 
>>
>> 
>>   > class="org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi">
>> 
>>   
>> 
>>
>> 
>>   
>> 
>>   > class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder">
>> 
>>   
>> 127.0.0.1:47500..47509
>>   
>> 
>>   
>> 
>>   
>> 
>>   
>> 
>>
>>
>> Below is my config for node from c++:
>> 
>>
>> 
>>
>> http://www.springframework.org/schema/beans;
>>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>>xmlns:util="http://www.springframework.org/schema/util;
>>xsi:schemaLocation="
>> http://www.springframework.org/schema/beans
>> http://www.springframework.org/schema/beans/spring-beans.xsd
>> http://www.springframework.org/schema/util
>> http://www.springframework.org/schema/util/spring-util.xsd;>
>> > class="org.apache.ignite.configuration.IgniteConfiguration">
>> 
>> 
>>
>> 

Re: Error running nodes in .net and c++

[Murthy Kakarlamudi]

Any help on this issue please...

On Sat, Apr 16, 2016 at 7:29 PM, Murthy Kakarlamudi 
wrote:

> Hi,
>In my use case, I am starting a node from .net which loads data from
> SQL Server table into cache upon start up. I have to read those entries
> from cache from a c++ node that acts as a client. I am getting the below
> error trying to start the node from c++.
>
> [19:08:57] Security status [authentication=off, tls/ssl=off]
> [19:08:58,163][SEVERE][main][IgniteKernal] Failed to start manager:
> GridManagerAdapter [enabled=true,
> name=o.a.i.i.managers.discovery.GridDiscoveryManager]
> class org.apache.ignite.IgniteCheckedException: Remote node has peer class
> loading enabled flag different from local [locId8=f02445af,
> locPeerClassLoading=true, rmtId8=8e52f9c9, rmtPeerClassLoading=false,
> rmtAddrs=[LAPTOP-QIT4AVOG/0:0:0:0:0:0:0:1, LAPTOP-QIT4AVOG/127.0.0.1,
> LAPTOP-QIT4AVOG/192.168.0.5,
> LAPTOP-QIT4AVOG/2001:0:9d38:90d7:145b:5bf:bb9b:11d9,
> LAPTOP-QIT4AVOG/2600:8806:0:8d00:0:0:0:1,
> /2600:8806:0:8d00:3ccf:1e94:1ab4:83a9,
> /2600:8806:0:8d00:f114:bf30:2068:352d]]
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.checkAttributes(GridDiscoveryManager.java:1027)
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.start(GridDiscoveryManager.java:680)
> at
> org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1505)
> at
> org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:917)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1688)
> at
> org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1547)
> at
> org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1003)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:534)
> at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:515)
> at org.apache.ignite.Ignition.start(Ignition.java:322)
> at
> org.apache.ignite.internal.processors.platform.PlatformAbstractBootstrap.start(PlatformAbstractBootstrap.java
>
> Below if my config for .net node:
> 
>
> http://www.springframework.org/schema/beans;
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>xsi:schemaLocation="
> http://www.springframework.org/schema/beans
> http://www.springframework.org/schema/beans/spring-beans.xsd;>
>class="org.apache.ignite.configuration.IgniteConfiguration">
> 
>   
> 
>   
> 
>
> 
>   
> 
>   
>   
>   
>   
>   
>   
>  class="org.apache.ignite.platform.dotnet.PlatformDotNetCacheStoreFactory">
>value="TestIgniteDAL.SQLServerStore, TestIgniteDAL"/>
> 
>   
>   
> 
>   
> 
> 
> 
> 
>   
> 
> 
> 
> 
> 
> 
>   
> 
> 
> 
>   
> 
>   
> 
>   
> 
>   
> 
>   
> 
>
> 
>class="org.apache.ignite.spi.communication.tcp.TcpCommunicationSpi">
> 
>   
> 
>
> 
>   
> 
>class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder">
> 
>   
> 127.0.0.1:47500..47509
>   
> 
>   
> 
>   
> 
>   
> 
>
>
> Below is my config for node from c++:
> 
>
> 
>
> http://www.springframework.org/schema/beans;
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>xmlns:util="http://www.springframework.org/schema/util;
>xsi:schemaLocation="
> http://www.springframework.org/schema/beans
> http://www.springframework.org/schema/beans/spring-beans.xsd
> http://www.springframework.org/schema/util
> http://www.springframework.org/schema/util/spring-util.xsd;>
>  class="org.apache.ignite.configuration.IgniteConfiguration">
> 
> 
>
> 
> 
> 
>  class="org.apache.ignite.configuration.CacheConfiguration">
> 
> 
> 
>
> 
>  class="org.apache.ignite.configuration.CacheConfiguration">
> 
> 
> 
> 
> 
> 
>
> 
> 
>  class="org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi">
> 
> 
> 
>  

Problems About Loadcache Streamer And Putall

[Level D]

Hi??


I've already read the development manul about these three methods. And it says 
that putall is inefficient when cluster loads a large nember of data.


Here comes my problems.


What are the advantages of localcache and streamer in big data? 
Are there any mesures to ensure data is not lost? Like at least once or only 
once...

Re: IgniteSemaphore problem

[Vladimir Ozerov]

Hi,

There was several issues associated with distributed semaphore in 1.5.0
release. As far as I know most of the will be fixed in 1.6.0 release.
Can you try building from current development master and see if the problem
is still there?

Vladimir.

On Wed, Apr 20, 2016 at 1:00 PM, swoky  wrote:

> now we have two nodes,
> created an IgniteSemaphore  in node A ,then we can use it in node B,
>
> but when node A down ,can't use it in node B any more,
>
> is there some Configurations i missed?
>
> below is my Configuration file
>
> -
> http://www.springframework.org/schema/beans;
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>xmlns:util="http://www.springframework.org/schema/util;
>xsi:schemaLocation="
> http://www.springframework.org/schema/beans
> http://www.springframework.org/schema/beans/spring-beans.xsd
> http://www.springframework.org/schema/util
> http://www.springframework.org/schema/util/spring-util.xsd;>
>
> 
>
> 
>  class="org.apache.ignite.configuration.CacheConfiguration">
>
> 
>
> 
> 
> 
>
>
> 
>  class="org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi">
> 
> 
> class="org.apache.ignite.spi.discovery.tcp.ipfinder.zk.TcpDiscoveryZookeeperIpFinder">
>  value="false" />
>  value="127.0.0.1:2181"/>
> 
> 
> 
> 
> 
> 
> 
> and the java code :
> ---
> Ignite ignite = Ignition.start("d:\x\ignite.xml");
>
> IgniteSemaphore semaphore = ignite.semaphore("semName", //
> Distributed
> semaphore name.
> 90, // Number of permits.
> true, // Release acquired permits if node,
> that owned them, left
> topology.
> true // Create if it doesn't exist.
> );
> -
>
>
>
> --
> View this message in context:
> http://apache-ignite-users.70518.x6.nabble.com/IgniteSemaphore-problem-tp4366.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>

Re: Getting a null pointer exception when trying to bulk load a cache using LoadCache

[Vladimir Ozerov]

Hi,

Could you please clarify what is ROCCache and ROCCacheConfiguration? And
how many nodes do you have in topology?

Vladimir.

On Thu, Apr 21, 2016 at 10:34 AM, abhishek94 
wrote:

> 1 client node and 1 remote server node, have added the Pojo jar and MYSQl
> jar
> in the remote node libs but still the loadcache throws an nullpointer
> exception.
>
> The code  is as follows
>
>   @Test
>   public void testClusterNormalCache() {
> Connection con = null;
> Statement stmt = null;
> String sql = null;
> IgniteCluster igniteCluster = rocCachemanager.getCluster();
> HashMap defaults = new HashMap();
> HashMap hmLocal = new HashMap();
> hmLocal.put("host", "10.113.56.231");
> hmLocal.put("port", 22);
> defaults.put("port", 22);
> hmLocal.put("uname", "root");
> hmLocal.put("passwd", "root123");
> hmLocal.put("nodes", 1);
> hmLocal.put("igniteHome",
> "/home/benakaraj/Downloads/apache-ignite-fabric-1.5.0.final-bin");
> hmLocal.put("cfg", "conf/spring_igniteConfig.xml");
> Collection> hosts = new ArrayList Object>>();
> hosts.add(hmLocal);
> try {
>   Collection result =
> igniteCluster.startNodes(hosts, defaults, true, 1, 2);
>   int waitTime = 0;
>   while (waitTime < 15000) {
> synchronized (this) {
>
>   try {
> wait(2000);
>   } catch (InterruptedException e) {
> // TODO Auto-generated catch block
> e.printStackTrace();
>   }
> }
>
> waitTime += 2000;
>   }
>   Collection ids = new ArrayList();
>   for (ClusterStartNodeResult res : result) {
> if (!res.isSuccess())
>   System.out.println(res.getError());
> else {
>   System.out.println(res.getHostName());
>   ClusterMetrics metrics = igniteCluster.metrics();
>   ClusterGroup group = igniteCluster.forRemotes();
>   // ClusterNode node=group.node();
>   Collection nodes = group.nodes();
>   System.out.println("Nodes--" + nodes.size());
>   for (ClusterNode node : nodes) {
> ids.add(node.id());
> Map hm = node.attributes();
> for (java.util.Map.Entry entry : hm.entrySet())
> {
>   // System.out.println(entry.getKey()+"---"+entry.getValue());
> }
>
>
> System.out.println("");
>
> System.out.println("");
>
> System.out.println("");
>
> System.out.println("");
>
>   }
>
>
> }
>   }
>   try {
> con = ds.getConnection();
>
> stmt = con.createStatement();
> sql = "create table Organization(org_id int,org_name
> varchar(20),primary key(org_id))";
> stmt.executeUpdate(sql);
> sql = "insert into Organization values(1,'Subex')";
> stmt.executeUpdate(sql);
> sql = "insert into Organization values(2,'Informatica')";
> stmt.executeUpdate(sql);
> sql = "insert into Organization values(3,'SAP')";
> stmt.executeUpdate(sql);
> sql = "insert into Organization values(4,'William O Niel')";
> stmt.executeUpdate(sql);
> sql = "insert into Organization values(5,'Subex1')";
> stmt.executeUpdate(sql);
> sql = "insert into Organization values(6,'Informatica1')";
> stmt.executeUpdate(sql);
> sql = "insert into Organization values(7,'SAP1')";
> stmt.executeUpdate(sql);
> sql = "insert into Organization values(8,'William O Niel1')";
> stmt.executeUpdate(sql);
> sql = "insert into Organization values(9,'Subex2')";
> stmt.executeUpdate(sql);
> sql = "insert into Organization values(10,'Informatica2')";
> stmt.executeUpdate(sql);
> sql = "insert into Organization values(11,'SAP2')";
> stmt.executeUpdate(sql);
> sql = "insert into Organization values(12,'William O Niel2')";
> stmt.executeUpdate(sql);
>   } catch (Exception e) {
>   }
>
>   try {
>
> ROCCacheConfiguration new4 = new
> ROCCacheConfiguration<>();
> new4.setName("loadCacheAll");
> new4.setCacheMode(CacheMode.REPLICATED);
> new4.setReadThrough(true);
> new4.setWriteThrough(true);
> JdbcType jdbcType = new JdbcType();
>
> jdbcType.setCacheName("loadCacheAll");
>
> jdbcType.setDatabaseSchema(con.getCatalog());
>
> jdbcType.setDatabaseTable("Organization");
> jdbcType.setKeyType(Integer.class);
> jdbcType.setValueType(Organization.class); // Key fields for
> PERSON.
>
> Collection keys = new 

Re: Ignite Installation with Spark under CDH

[Vladimir Ozerov]

Hi,

Could you please clarify the exact problem? Do you see any exception?

Vladimir.

On Fri, Apr 22, 2016 at 4:57 PM, mdolgonos 
wrote:

> I'm trying to install and integrate Ignite with Spark under CDH by
> following
> the recommendation at
> https://apacheignite-fs.readme.io/docs/installation-deployment for
> Standalone Deployment. I modified the existing
> $SPARK_HOME/conf/spark-env.sh
> as recommended but the following command still can't recognize  the ignite
> package
> import org.apache.ignite.configuration._
> Can somebody advise if I'm missing anything?
> Thank you,
>
>
>
> --
> View this message in context:
> http://apache-ignite-users.70518.x6.nabble.com/Ignite-Installation-with-Spark-under-CDH-tp4457.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>

Re: Detecting a node leaving the cluster

[Vladimir Ozerov]

Ralph,

EVT_NODE_LEFT and EVT_NODE_FAILED occur on local node. They essentially
mean "I saw that remote node went down".

Vladimir.

On Sat, Apr 23, 2016 at 5:48 PM, Ralph Goers 
wrote:

> Some more information that may be of help.
>
> Each user of a client application creates a “session” that is represented
> in the distributed cache. Each session has its own connection to the third
> party application. If a user uses multiple client applications they will
> reuse the same session and connection with the third party application. So
> when a single node goes down all the user’s sessions need to become “owned”
> by different nodes.
>
> In the javadoc I do see IgniteEvents.localListen(), but the description
> says it listens for “local” events. I wouldn’t expect EVT_NODE_LEFT or
> EVT_NODE_FAILED to be considered local events, so I am a bit confused as to
> what the method does.
>
> Ralph
>
> On Apr 23, 2016, at 6:49 AM, Ralph Goers 
> wrote:
>
> From what I understand in the documentation client mode will mean I will
> lose high availability, which is the point of using a distributed cache.
>
> The architecture is such that we have multiple client applications that
> need to communicate with the service that has the clustered cache. The
> client applications expect to get callbacks when events occur in the third
> party application the service is communicating with. If one of the service
> nodes fail - for example during a rolling deployment - we need one of the
> other nodes to re-establish the connection with the third party so it can
> continue to monitor for the events. Note that the service servers are
> load-balanced so they may each have an arbitrary number of connections with
> the third party.
>
> So I either need a listener that tells me when one of the nodes in the
> cluster has left or a way of creating the connection using something ignite
> provides so that it automatically causes the connection to be recreated
> when a node leaves.
>
> Ralph
>
>
> On Apr 23, 2016, at 12:01 AM, Владислав Пятков 
> wrote:
>
> Hello Ralph,
>
> I think the correct way is to use client node (with setClientMode - true)
> for control of cluster. Client node is isolated from data processing and
> not subject fail of load.
> Why are you connect each node with third party application instead of to
> do that only from client?
>
> On Sat, Apr 23, 2016 at 4:10 AM, Ralph Goers 
> wrote:
>
>> I have an application that is using Ignite for a clustered cache.  Each
>> member of the cache will have connections open with a third party
>> application. When a cluster member stops its connections must be
>> re-established on other cluster members.
>>
>> I can do this manually if I have a way of detecting a node has left the
>> cluster, but I am hoping that there is some other recommended way of
>> handling this.
>>
>> Any suggestions?
>>
>> Ralph
>>
>
>
>
> --
> Vladislav Pyatkov
>
>
>
>

Re: java.lang.OutOfMemoryError in normal Ignite usage

[Vladimir Ozerov]

Hi,

Most probably, you just have insufficient heap, as queries require some
heap space during execution. Probably you should give your node more heap
and monitor it for some. If all is fine, you will see a saw-like pattern -
when memory is allocated and then release. If there is a leak, you will see
constant heap growth.

Vladimir.

On Sun, Apr 24, 2016 at 1:53 AM, Eduardo Julian 
wrote:

> Hi, everyone.
>
> I started a program 3 days ago on a server with 1GB RAM.
>
> Everything was running smoothly until a couple of hours ago, when the
> service wasn't responding.
> When we go check the logs, there is an OOMError with an Ignite stack-trace
> tagging along.
>
> All that I store on that server is stored on Ignite (with read-through and
> write-through to a MySQL DB).
> It's fairly light stuff, just some objects with 10+ fields, and it's just
> 1 cache right now.
>
> However, in the logs, the bulk of the operations preceding the OOM error
> were read-operations that neither created nor updated the data on Ignite.
> Just performed some queries.
>
> And yet, for some reason, there was a HashMap being updated somewhere,
> which triggered the OOM error.
>
> Check it out:
>
> Apr 23, 2016 4:35:44 PM org.apache.ignite.logger.java.JavaLogger error
> SEVERE: Caught unhandled exception in NIO worker thread (restart the node).
> java.lang.OutOfMemoryError: Java heap space
> at java.util.HashMap$KeySet.iterator(HashMap.java:912)
> at java.util.HashSet.iterator(HashSet.java:172)
> at
> java.util.Collections$UnmodifiableCollection$1.(Collections.java:1039)
> at
> java.util.Collections$UnmodifiableCollection.iterator(Collections.java:1038)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.checkIdle(GridNioServer.java:1489)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:1406)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1280)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.Thread.run(Thread.java:745)
>
> Apr 23, 2016 4:35:45 PM org.apache.ignite.logger.java.JavaLogger error
> SEVERE: Runtime error caught during grid runnable execution: GridWorker
> [name=grid-nio-worker-0, gridName=null, finished=false, isCancelled=false,
> hashCode=1645791145, interrupted=false, runner=grid-nio-worker-0-#40%null%]
> java.lang.OutOfMemoryError: Java heap space
> at java.util.HashMap$KeySet.iterator(HashMap.java:912)
> at java.util.HashSet.iterator(HashSet.java:172)
> at
> java.util.Collections$UnmodifiableCollection$1.(Collections.java:1039)
> at
> java.util.Collections$UnmodifiableCollection.iterator(Collections.java:1038)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.checkIdle(GridNioServer.java:1489)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.bodyInternal(GridNioServer.java:1406)
> at
> org.apache.ignite.internal.util.nio.GridNioServer$AbstractNioClientWorker.body(GridNioServer.java:1280)
> at
> org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
> at java.lang.Thread.run(Thread.java:745)
>
> Apr 23, 2016 4:35:46 PM org.apache.ignite.logger.java.JavaLogger error
> SEVERE: Runtime error caught during grid runnable execution: GridWorker
> [name=partition-exchanger, gridName=null, finished=false,
> isCancelled=false, hashCode=685490869, interrupted=false,
> runner=exchange-worker-#45%null%]
> java.lang.OutOfMemoryError: Java heap space
> at java.util.HashMap.newNode(HashMap.java:1734)
> at java.util.HashMap.putVal(HashMap.java:630)
> at java.util.HashMap.put(HashMap.java:611)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionMap2.put(GridDhtPartitionMap2.java:112)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionMap2.(GridDhtPartitionMap2.java:96)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionFullMap.(GridDhtPartitionFullMap.java:107)
> at
> org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.partitionMap(GridDhtPartitionTopologyImpl.java:841)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.sendAllPartitions(GridCachePartitionExchangeManager.java:747)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.refreshPartitions(GridCachePartitionExchangeManager.java:698)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.refreshPartitions(GridCachePartitionExchangeManager.java:724)
> at
> org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager.access$1600(GridCachePartitionExchangeManager.java:107)
> at
> 

Re: Compute Grid API in C++/Scala

[Vladimir Ozerov]

Hi Arthi,

I think C++ Compute API will be ready somewhere around 1.7 version. Exact
timeline is not know for now, but I think this is a matter of several
months.

Vladimir.

On Mon, Apr 25, 2016 at 8:47 AM, arthi 
wrote:

> Thanks Igor & Val.
>
> Is there a tentative timeline when the next release with C++ compute grid
> will come out?
>
> Thanks,
> Arthi
>
>
>
> --
> View this message in context:
> http://apache-ignite-users.70518.x6.nabble.com/Compute-Grid-API-in-C-Scala-tp4456p4487.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>

Re: Compute Grid API in C++/Scala

[arthi]

Thanks Igor & Val. 

Is there a tentative timeline when the next release with C++ compute grid
will come out?

Thanks,
Arthi



--
View this message in context: 
http://apache-ignite-users.70518.x6.nabble.com/Compute-Grid-API-in-C-Scala-tp4456p4487.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.