WAL log folder issue in YARN mode

When I deployed ignite as a YARN application with persistent store enabled. The WAL logs are under the /yarn/nm/usercache/username/appcache/application_appid/container_containerID/ignite/apache-ignite-fabric-2.1.0-bin/work/db/wal/. But when ignite is restarted using YARN, a new appid will be create

Re: Job Listeners

Hello Alexey, thanks a lot for the input it was very useful, there are two more things i m stuck at: 1. when i run the above in cluster environment(with more than one node) with value as an object in session.setAttribute(key, value) value being an object, then i m unable to proceed further as one

Re: Re: Exception use affinity key when put #invoke from Client.

Thanks Denis. We customized own BinaryConfiguration, which include this AssetKey, when I removed this seem can work now. Regards Aaron aa...@tophold.com From: Denis Mekhanikov Date: 2017-09-20 00:36 To: user Subject: Re: Exception use affinity key when put #invoke from Client. Hi Aaron!

Re: REST API response json is empty.

Any luck with my query? What am i missing? Why REST response is blank though the cache has data, i tried scan on visor i can see the data over there. Thanks, Anji. On 19 Sep 2017 00:26, "ANJANEYA PRASAD NIDUBROLU" wrote: > Hello All, > > Hope you are doing great!. > > I have tried Ignite's REST

CacheStoreAdapter#loadAll and ContinuousQuery

I've got an implementation of CacheStoreAdapter that appears to be working (it's persisting items etc..). I also have a ContinuousQuery setup and an initialQuery that runs after the impls loadAll(). Before I started using my own impl of CacheStoreAdapter - the ContinuousQuery worked as expected, bu

Re: Conflicting cross-version suffixes in: org.scalatest:scalatest, com.twitter:chill, org.apache.spark:spark-unsafe, org.apache.spark:spark-tags

Looks like you use Scala 2.10 and corresponding Spark libraries. In this case you should use 'ignite-spark_2.10' Ignite module instead of just 'ignite-spark'. -Val -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Does Ignite write READ operations of Txs to WAL?

No, reads are not appended to WAL. It is designed for recovery, not for auditing purposes. -Val -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Does Ignite write READ operations of Txs to WAL?

Hi, Does Ignite write READ operations of transactions (e.g. for future auditing purposes) in the WAL? Thanks,

Conflicting cross-version suffixes in: org.scalatest:scalatest, com.twitter:chill, org.apache.spark:spark-unsafe, org.apache.spark:spark-tags

I am hitting this error when I add ignite-spark 2.2.0 artifact to by project. [error] Modules were resolved with conflicting cross-version suffixes in {file://ignite-poc/}ignite-poc: [error]org.scalatest:scalatest _2.11, _2.10 [error]com.twitter:chill _2.11, _2.10 [error]org.apache.spa

Re: Exception use affinity key when put #invoke from Client.

Hi Aaron! Is it possible that you wrote a value to cache before configuring an affinity key? This exception occurs when configuration of affinity key for a sought key doesn't match configuration that is stored in cache. Maybe you have persistence enabled and you wrote the value before adding @Affi

Re: Existing queue can't be accessed on client node

Hi again, I filed a bug about the issue you described: https://issues.apache.org/jira/browse/IGNITE-6437 Thanks, Mike. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Exception use affinity key when put #invoke from Client.

hi all, We using the affinity key map to affinity cache connected, the key is a very simple class: class AssetKey @AffinityKeyMapped private String accountId; private String transId; But every time when run this command from client: ignite.cache(AssetEntry.IG_CACHE_NAME).invoke(new AssetK

Re: Ignite YARN deployment mode issues

Figured the second question out by myself. The node I'm running ./control.sh does not seem to have ignite grid started. Here's the yarn log. [08:09:30,866][SEVERE][main][IgniteKernal] Exception during start processors, node will be stopped and close connections class org.apache.ignite.IgniteExce

Ignite YARN deployment mode issues

I'm using ignite 2.1, my ignite config xml is as follows. And in standalone mode, ignite can read the log4j2.xml in local directory and works ok. When deployed in YARN, ignite says it can fi

Re: work around for problem where ignite query does not include objects added into Cache from within a transaction

Hi Thanks for your responses. I just wanted a temporary work around till the actual feature is implemented, even at the cost of performance. I have thought of another approach to this problem. I plan to use my own transaction mechanism instead of Ignite transactions. I can use explicit locks to

回复： Fetched result set too large

I see. Thanks a lot! 2017年09月19日 13:49,slava.koptilin : Hi Lucky, You just need to start grid with -DIGNITE_SQL_MERGE_TABLE_MAX_SIZE=3 JVM flag. Thanks, Slava. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/