java.lang.OutOfMemoryError: Java heap space

Hi, Following is my Metrics for local node but getting out of memory exception (details below). Metrics for local node (to disable set 'metricsLogFrequency' to 0) ^-- Node [id=80a92be0, name=null, uptime=00:01:00:001] ^-- H/N/C [hosts=1, nodes=1, CPUs=8] ^-- CPU [cur=13.4%,

Re: Ignite cache range query using cache keys

> On Feb 21, 2017, at 11:48 PM, diopek wrote: > > Hi Denis, > we have ignite cache that has key value pair as the following; > IgniteCache> > and cache cofiguration for this cache is as the following; > CacheConfiguration>

Re: Ignite cache range query using cache keys

Basically, we just need indexing on keys, as we only query via keys (which is Long type). Value is is ArrayList which we don't need to query. Is there any way to add index only on keys. -- View this message in context:

Re: Ignite cache range query using cache keys

Hi Denis, we have ignite cache that has key value pair as the following; IgniteCache> and cache cofiguration for this cache is as the following; CacheConfiguration> cacheCfg = new CacheConfiguration<>(cacheName);

Re: GROUP_CONCAT function is unsupported

Related to the question: http://apache-ignite-users.70518.x6.nabble.com/List-of-supported-SQL-functions-same-as-H2-td10722.html -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/GROUP-CONCAT-function-is-unsupported-tp10757p10784.html Sent from the Apache Ignite

IGNITE-2680

Hi, IGNITE-2680 says it is resolved. Would it be available in 1.9 ? I see following code in 1.8. @Override public void setQueryTimeout(int timeout) throws SQLException { ensureNotClosed(); throw new SQLFeatureNotSupportedException("Query timeout is not supported."); }

Re: NOT IN in ignite

Hi Val, I agree with you. Controlling query execution plan as per query is useful in this case. collocation = true does not make sense for queries without join though caches are collocated. what do you say ? i feel query executor must be intelligent enough to use collection as per query.

what is the message guaranteed level about distributed messaging

I think there are 3 message guaranteed levels. 1. one message will be received at least once. 2. one message will be received exactally once. 3. one message will be received at most once. I want to know what is the message guaranteed level about distributed messaging. -- View this message in

Re: Monitoring Cache - Data counters, Cache Data Size

Hi Val, I saw that MBean, but it reports the same number as the Local MBean. and if I go on each node, the CacheCluster and CacheLocal Cache size matches. I do not see a sum total across all nodes. Thanks, Binti -- View this message in context:

Re: Pessimistic TXN did not release lock on a key, all subsequent txns failed

Attaching the console log file too, it has the above error. Unfortunately we lost the files for older updates to this key now, they rolled over. Ignite-Console-1.zip but the "Transaction has been already

Re: Pessimistic TXN did not release lock on a key, all subsequent txns failed

Hi, I will try this code the next time this issue happens. Attaching one nodes full logs. It has a lot of info. Ignite-11221.gz However, I found this on the console logs on the first exception that occurred. Is this

Re: NOT IN in ignite

Anil, OK, so you're talking about setting collocated flag on per query level in JDBC driver, right? This makes sense, but it seems to be a limitation of JDBC API rather than Ignite implementation. How would you provide a parameter when creating a statement and/or executing a query? Do you have

Re: unicode character with apache ignite with multiple nodes

Hi, Please properly subscribe to the mailing list so that the community can receive email notifications for your messages. To subscribe, send empty email to user-subscr...@ignite.apache.org and follow simple instructions in the reply. babak wrote > I'm trying to cache my unicode data using

Re: Monitoring Cache - Data counters, Cache Data Size

Binti, These metrics are exposed via CacheClusterMetricsMXBeanImpl. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Monitoring-Cache-Data-counters-Cache-Data-Size-tp3203p10775.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: List of supported SQL functions (same as H2?)

Sergi, Is there any technical reason that prevents us supporting GROUP_CONCAT? — Denis > On Feb 21, 2017, at 2:46 AM, zaid wrote: > > > Yes, everything that is supported in H2 available in Ignite. > > GROUP_CONCAT is not working for me: > > Please find below

Re: simple file based persistent store support TTL

What is the exception message? Your trace is truncated. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/simple-file-based-persistent-store-support-TTL-tp10355p10773.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: Questions on Ignite Clients

abdul shareef wrote > Thanks Val. Is there a way to disable the startup message on the client > nodes? Not completely, bur you can disable the ASCII logo by setting -DIGNITE_NO_ASCII=true system property. -Val -- View this message in context:

Re: persist periodically

Shawn, If it's a standalone node, you can just terminate the process. There is a shutdown hook that will gracefully stop the node. For example, kill command (without -9) will do the job. For embedded node call Ignition.stop(). -Val -- View this message in context:

Re: getOrCreateCache hang

There were some coding errors in the previous attachment. The previous code still illustrates the deadlock, but the attached correctly stores data in tables. I've also included the test input file, for completeness. testCode.gz

Re: getOrCreateCache hang

There is only one Ignite server in my testing and two clients. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/getOrCreateCache-hang-tp10737p10769.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: getOrCreateCache hang

Attached is a file containing the outputs (stack trace, Ignite log) and two Maven test files. test+output.gz I'm hoping you can tell me I'm just doing something silly to provoke this... Thanks! Matt -- View this

How to configure MongoDB Client? I'm getting NotSerializableException

Hi, I have the same problem mentioned in the post below, but I use mongoDb instead of CacheJdbcBlobStore. http://apache-ignite-users.70518.x6.nabble.com/How-to-use-CacheJdbcBlobStore-Getting-NotSerializableException-td431.html Here is an example with Mongo, but it use Embedded MongoDB which

Re: Pessimistic TXN did not release lock on a key, all subsequent txns failed

There are no something suspicious in stack trace. You can check that key is locked using IgniteCache.isLocalLocked() method. For remote nodes you can run task that performs this checking. Could you please provide full logs for analysis? On Tue, Feb 21, 2017 at 6:48 PM, bintisepaha

Re: Pessimistic TXN did not release lock on a key, all subsequent txns failed

Andrey, thanks for getting back. I am attaching the stack trace. Don't think the cause is a deadloc, but the trace is long so maybe I am missing out something, let me know if you find something useful. We cannot ourselves reproduce this issue as there are no errors on the prior successful update.

Re: Ignit Cache Stopped

I think it is just H2 wrapper for string values. On Tue, Feb 21, 2017 at 8:21 AM, Anil wrote: > Thanks Andrey. > > I see node is down even gc log looks good. I will try to reproduce. > > May I know what is the org.h2.value.ValueString objects in the attached the > screenshot

Re: Task was not deployed error

Hi! Try to enable peer class loading (by IgniteConfiguration#setPeerClassLoadingEnabled to *true) *or deploy task classes on all nodes manually (put jars with classes to all ignite\libs folder). It would be great if you can share a maven project which reproduce this case. On Mon, Feb 20, 2017 at

Re: How to support Sql string operations IN and Regex

IN queries and their alternative with temporary table are described there: https://apacheignite.readme.io/docs/sql-performance-and-debugging#section-sql-performance-and-usability-considerations Ignite uses H2 SQL engine, which supports regular expressions:

How to support Sql string operations IN and Regex

Following is my current query for *OrderCache*, using a Sql *like* operator *var fieldsQuery = orderCache.QueryFields(new SqlFieldsQuery("select Top 10 OrderId, OrderName from OrderEntity Where OrderName like '%' || ? || '%' Order By OrderId", orderNameValue));* As per my understanding this will

Re: getOrCreateCache hang

Hi, Could you share logs and thread dumps from all nodes from cluster? If you can create and share a maven project which reproduce your problem then it would be great! Thanks, Nikolay On Mon, Feb 20, 2017 at 8:35 PM, Matt Warner wrote: > I'm experiencing Ignite

Re: Cache write behind optimization

Hi Yakov, I am trying to process data based on primary node calculation using mapKeyToNode function of cache's affinity function. I expect there is no remote access. I will try to summarize problem into a reproducible code piece. Thanks for your help. On Tue, Feb 21, 2017 at 11:09 AM, Yakov

GROUP_CONCAT function is unsupported

Hi, Any reason why GROUP_CONCAT function is unsupported? Please find below code snippet from ignite-indexing module: class file: GridSqlAggregateFunction line no: 84 switch (type) { case GROUP_CONCAT: throw new UnsupportedOperationException(); Regards.

Re: List of supported SQL functions (same as H2?)

Yes, everything that is supported in H2 available in Ignite. GROUP_CONCAT is not working for me: Please find below code snippet from ignite-indexing module: class file: GridSqlAggregateFunction line no: 84 switch (type) { case GROUP_CONCAT: throw new

Re: Flink Streamer Compatibility.

ignite-flink is a thin, one-class module, and yes, it's compatible with newest Apache Flink versions. -Dmitry. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Flink-Streamer-Compatibility-tp10727p10755.html Sent from the Apache Ignite Users mailing list archive

Re: Cache write behind optimization

Tolga, this looks like you do cache.get() and key resides on remote node. So, yes, local node waits for response from remote node. --Yakov 2017-02-21 10:23 GMT+03:00 Tolga Kavukcu : > Hi Val,Everyone > > I am able to overcome with write behind issue and can process