Transaction return value problem

Ignite enables transactions to determine how to perform certain operations after a successful transaction is executed, is transaction propagation currently supported, and how to inherit from Spring's transactions? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Graph Database with Ignite? Search like Elastic search/Apache Solr with Ignite?

Thanks! You will think graph (edges and vertex), graph traversal, could be added to ignite. Actually that was my next question, is it possible to add a search (like elastic search or apache solr) on top of all those ignite tables? From: Jörn Franke Reply-To: "user@ignite.apache.org" Date:

Re: two data region with two nodes

Thank you for your answer, Maybe I use region config the wrong way. There are two apps(more apps with different roles) with different ignite configs, first App :set default region with persistence enable :set cache a,with nodefilter in first apps,default region second app :set

Re: Is IgniteBiInClosure instance thread safe?

Yes, it's thread-safe and you can implement multi-threaded cache store Evgeni 2018-08-01 18:15 GMT+03:00 Prasad Bhalerao : > Hi, > > I am loading caches from oracle tables. For that I am > overriding CacheStoreAdapter.loadCache method. > This method accepts parameter IgniteBiInClosure. > > Is

Is IgniteBiInClosure instance thread safe?

Hi, I am loading caches from oracle tables. For that I am overriding CacheStoreAdapter.loadCache method. This method accepts parameter IgniteBiInClosure. Is the instance of IgniteBiInClosure instance thread safe? I am doing partition aware loading and I have written code as shown below.

Re: loadCache is not returning the same number of records for every restart of the server

How do you check number of records in the cache and at what moment? Maybe your method of measurement doesn't give you actual results? It is also possible, that page eviction is kicking in and removes your data, since there is

Re: node becoming inactive

Tim, Server nodes do not try to reconnect to the cluster. Only clients do. Denis ср, 1 авг. 2018 г. в 17:52, Tim Dudgeon : > OK, thanks. Will investigate the possibility. > > If this is caused by a network timeout or long GC pause as you suggested, > shouldn't the node be expected to rejoin

Re: SqlFieldsQuery Cannot create inner bean 'org.apache.ignite.cache.query.SqlFieldsQuery

Great, It works perfectly, thankyou. Bhaskar -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: node becoming inactive

OK, thanks. Will investigate the possibility. If this is caused by a network timeout or long GC pause as you suggested, shouldn't the node be expected to rejoin the cluster once the problem has gone away? On 01/08/18 15:46, Denis Mekhanikov wrote: Tim, This is strange, since

Re: node becoming inactive

Tim, This is strange, since *failureDetectionTimeout* and *clientFailureDetectionTimeout* are pretty important properties and Ignite maintainers encourage users to tune timeouts using them. I think, you should send a feature request to Nextflow and ask them to add this property to configuration.

Re: Ignite Cache Expiry policy does not remove the cache from cache lists

There is no such mechanism. Caches are rather static structured. They are not supposed to be created or removed too often. Cache creation and destruction are cluster-wide operations, that make all operations stop until they are finished. But if you really want to do it, you can schedule a task,

Re: node becoming inactive

Hi Yes, I saw that property, but: 1. I wasn't sure what the default was and what to use for a more tolerant value 2. The Nextflow framework does not seem to allow to set this. Only these Ignite params seem to be controllable: https://www.nextflow.io/docs/latest/ignite.html#advanced-options

Re: node becoming inactive

As per failing node: looks like it failed due to a network issue or a long GC pause. Try increasing value of IgniteConfiguration.html#clientFailureDetectionTimeout

Re: SqlFieldsQuery Cannot create inner bean 'org.apache.ignite.cache.query.SqlFieldsQuery

Hello! You have to put export before it to pass it to Apache Ignite: export IGNITE_SQL_FORCE_LAZY_RESULT_SET=true Regards, -- Ilya Kasnacheev 2018-08-01 16:58 GMT+03:00 ApacheUser : > Hello Ilya Kasnacheev, > > I set IGNITE_SQL_FORCE_LAZY_RESULT_SET=true just below > ENABLE_ASSERTIONS="0"

Re: c++ data streamer api

Hi, 1) Yes, it is really missing. 2) It is "we haven’t got around to it yet" case. There are not so much C++ contributes. Best Regards, Igor On Wed, Aug 1, 2018 at 12:46 PM Floris Van Nee wrote: > Hi all, > > > > I’m looking into using Ignite and noticed the C++ API seems to be missing >

Re: node becoming inactive

Tim, By default IP finder cleans unreachable addresses from the registry once per minute. You can change this frequency by setting a different value to TcpDiscoverySpi.html#setIpFinderCleanFrequency

Re: SqlFieldsQuery Cannot create inner bean 'org.apache.ignite.cache.query.SqlFieldsQuery

Hello Ilya Kasnacheev, I set IGNITE_SQL_FORCE_LAZY_RESULT_SET=true just below ENABLE_ASSERTIONS="0" in ignite.sh but still I am getting out of memory error when I do select * from table. Is this right place to set this parameter? please confirm. Thanks -- Sent from:

Re: AssertionError while executing SQL

Prasad, This is a bug. It doesn't let you use fields of sub-select results in WHERE conditions. I filed a JIRA ticket for it: IGNITE-9156 Thank you for the report! You can embed the equality condition into the sub-select to avoid this problem.

Re: SqlQueryFileds on List of Binary Object

Hi, As for now, it's not possible to query objects if they're stored as collection like IgniteCache >, so, I'd recommend changing the way how you store objects in cache - it will be pretty the same if you will store it like IgniteCache Evgenii -- Sent from:

Re: Ignite Server nodes crash with OutOfMemoryError on cluster upscale

Artem, Heap space, required by Ignite depends on the workload, that you perform on the cluster. Usually SQL is the most memory-consuming part. I can't say, what causes the node failure in your case. When cluster topology changes, data rebalancing is triggered. It may pollute the heap space. You

Re: Cache updates to nodes in client mode

Gordon, There is already a mechanism in discovery protocol, that makes client nodes to be disconnected from cluster in case, when they don't respond for a long time. It can be configured using IgniteConfiguration#clientFailureDetectionTimeout

Re: SQL exeucution in ignite

Prasad, > 1) What happens if the index is present filter column and sort column? If there is an index on a needed column, then Ignite doesn't have to sort data again. It just can use the index. > If ignite pulls all data in heap then what the use of page size property Page size specifies the

AssertionError while executing SQL

I am getting Assertion error while executing following SQL. Please check this highlighted part which causing this error. Can someone please advise? Is this a bug or am I doing something wrong? SELECT tmp.assetGroupId, tmp.name, tmp.businessImpact, tmp.userId , tmp.modifiedBy,

Re: Help needed with BinaryObjectException

It happens after we redeploy the application. There might be changes to our model, in this scenario an enum is the problem, we added values to it. We switched persistence of. We currently have multiple instances of our application running. We redeploy them one by one so we can guarantee 24/7

c++ data streamer api

Hi all, I'm looking into using Ignite and noticed the C++ API seems to be missing functionality for data streaming (Java IgniteDataStreamer together with the StreamReceiver/StreamVisitor/StreamTransformer classes). Without these, I assume it is not going to be easy to stream large amounts of

Re: Help needed with BinaryObjectException

Hi, We do not have persistence. How can I purge the metadata? Can I purge the metadata runtime? If we have multiple instances of the application running, and we need to be 24/7 up, we can't shutdown all instances at once, but this suggest that using Ignite, that is NOT possible! Am I correct

node becoming inactive

I'm hitting a strange problem when using an ignite cluster for performing compute jobs. Ignite is being managed by the underlying Nextflow tool (https://www.nextflow.io/docs/latest/ignite.html) and I don't understand the precise details of how this is set up, but I believe there's nothing

The Apache Ignite Book

Dear, Users. Yesterday the first portion of our new title The Apache Ignite Book had been published and available at https://leanpub.com/ignitebook . The full table of contents and the sample chapter is also available through leanpub . The title is an agile