“Failed to communicate with Ignite cluster" error when using JDBC Thin driver

Hi guys, When I use ignite jdbc thin driver connect Ignite cluster, sometimes will meet the errors below. Do you have any idea what cause this error? many thanks! org.springframework.dao.DataAccessResourceFailureException: ### Error updating database. Cause: java.sql.SQLException: Failed to

Re: Upgrade from 2.2.0 to 2.3.0 problem with BinaryObjectException

Hi Łukasz! This problem is caused by *@Cacheable* annotation on *SampleRepo#getSampleEntity() *method. When you invoke it for the first time, its result is put into an Ignite cache. And for the second time the result is just taken from the cache, you probably know that. The problem is that

Re: NullPointerException in GridDhtPartitionDemander

Hello! Can you please elaborate why do you have acute number of topology versions (69 in this case)? Can you please describe the life cycle of your topology? Which nodes join, when, which nodes leave, when? Don't you, by any chance, create client nodes for every request or small batch, or even

Re: Upgrade from 2.2.0 to 2.3.0 problem with BinaryObjectException

Oh, looks like this problem is already fixed: https://issues.apache.org/jira/browse/IGNITE-6944 I checked, your project works, when Ignite from current master is used. So, you can just wiat for the next release and switch to it. Denis ср, 20 дек. 2017 г. в 13:10, Denis Mekhanikov

Re: Group By Query is slow : Apache Ignite 2.3.0

Hi, How many records your query returns without LIMIT? How long does it take to select all records without grouping? Thanks! -Dmitry -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Memory foot print of the ignite nThe background cache eviction process was unable to free [10] percent of the cache for Context

Hi Naveen, Off-heap memory "Off-heap size" works strangely. There are several tickets here https://issues.apache.org/jira/browse/IGNITE-6814 https://issues.apache.org/jira/browse/IGNITE-5583 http://apache-ignite-users.70518.x6.nabble.com/Cache-size-in-Memory-td17226.html You can get an

Re: List of running Continuous queries or CacheEntryListener per cache or node

Crossposting to devlist. Hi Igniters! It's might be a nice feature to have - get list of registered continuous queries with ability to deregister them. What do you think? Thanks! -Dmitry 20.12.2017 16:59, fefe пишет: For sanity checks or tests. I want to be sure that I haven't forgot to

Re: Group By Query is slow : Apache Ignite 2.3.0

Hi Indranil, These measurements are not fully correct, for example select count(*) might use only index and in select * was not actually invoked, because you need to run over cursor. Also by default query is not parallelized on one node, and scan with grouping is going sequentially in one

Re: Data load is very slow in ignite 2.3 compare to ignite 1.9

Why are you giving only 5GB of RAM to every node then (referring to your data region configuration)? You mentioned that it’s fine to assign 15GB of RAM. Does it mean there are another processes running on the server that use the rest of RAM heavily. To make the troubleshooting of your problem

Re: NullPointerException in GridDhtPartitionDemander

Hi, A client gets created for each request and client connect to cluster to read the data. Once reading is done, client exits. This explains the high topology version. Though server nodes are not getting created often. We can try Ignite 2.3 in next release but we are close to our release date

Re: List of running Continuous queries or CacheEntryListener per cache or node

For sanity checks or tests. I want to be sure that I haven't forgot to deregister any listener. Its also very important metric to see how many continuous queries/listeners are currently running. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: “Failed to communicate with Ignite cluster" error when using JDBC Thin driver

Hi, Is it possible that version of thin driver is different from version of cluster nodes? Does it happen on concrete queries or it could be on any one? Thanks! -Dmitry -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite 2.3 Swap Path configuration is causing issue

My understanding is specifying a swapPath makes data region allocated in a memory mapped file. Otherwise the data region is stored in off-heap RAM. swapPath is not about swap files used by operating systems to extend RAM. According to my understanding the behaviour you described is correct.

Ignite 2.3 Swap Path configuration is causing issue

Hi All, We are migrating from 1.9 to 2.3 and we are configuring Data regions for Cache with '*swapPath*' configuration as below. < property name="initialSize" value="#{100L * 1024 * 1024}" /> ** Now as per configs, first data (< = 5GB) should go in RAM and once it starts spilling

List of running Continuous queries or CacheEntryListener per cache or node

Is it possible to get list of running continuous queries or cacheEntryListener for given Cache or given Node? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: List of running Continuous queries or CacheEntryListener per cache or node

Hi, Currently it's not possible. What's for do you need such possibility? Thanks! -Dmitry -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Data load is very slow in ignite 2.3 compare to ignite 1.9

Hi All, We are migrating from 1.9 to 2.3 and following are the respective configs . *Cache Config in 1.9:* < property name="backups" value="0" /> java.lang.String net.juniper.cs.entity.InstallBase *Cache Config in 2.3:* Here we have to configure DataRegion and then that data

Re: Ignite 2.3 Swap Path configuration is causing issue

Hi Alexey, Thanks for quick reply. Since you are suggesting that SwapPath is not about swap files used by operating systems to extend RAM. Please suggest me the way in 2.3 to configure swapfiles to extend RAM Thanks & Regards Tejas On 20 Dec 2017 9:29 pm, "Alexey Kukushkin"

Re: Data load is very slow in ignite 2.3 compare to ignite 1.9

Specifying "swapPath" makes Ignite use memory mapped file to store data. Memory mapped files are slower than "raw" RAM. Remove "swapPath" setting to have same configuration as you had in Ignite 1.9 (data stored in off-heap RAM).

Re: Data load is very slow in ignite 2.3 compare to ignite 1.9

Yes, I have same cluster, env and no of nodes. I am using DataStreamer to load data. Thanks and Regards Tejas On 21 Dec 2017 12:11 am, "Alexey Kukushkin" wrote: > Tejas, how do you load the cache - are you using DataStreamer or SQL, JDBC > or put/putAll or something

Re: Ignite 2.3 Swap Path configuration is causing issue

Swapping feature was removed in Ignite v.2 since native persistence was introduced. Use native persistence to "extend" memory.

Re: Performance comparisons

If 3-rd party runs benchmark even better. It doesn't make sense if everyone in the world has to run the same benchmarks. Division of labor makes sense. Here's what I meant w.r.t. comparison vs Hazelcast.

Re: Data load is very slow in ignite 2.3 compare to ignite 1.9

Tejas, how do you load the cache - are you using DataStreamer or SQL, JDBC or put/putAll or something else? Can you confirm - are you saying you have same cluster (same number of nodes and hardware) and after the upgrade the cache load time increased from 40 to 90 minutes?

Re: Data load is very slow in ignite 2.3 compare to ignite 1.9

Memory architecture changed in release 2 and one of the consequences was Ignite now allocates memory more eagerly. Do you have enough memory on the servers? Is it possible that the amount of memory you allocated for Ignite results in Ignite reserving too much RAM on the servers so that the

Re: Group By Query is slow : Apache Ignite 2.3.0

Hi,     There are 86486 records.   Time taken for select count(*) from A => 35 ms Time taken for select mainId, count(*) from A group by mainId => 70 ms Time taken for select * from A => 0 ms  I am doing a POC with apache ignite and I am very keen to use it in production for live streaming and

Re: “Failed to communicate with Ignite cluster" error when using JDBC Thin driver

It could not be a version issue, the thin driver and cluster version are exactly same. It can happened on any query but can not be reproduce 100%, it only happened "some times". In Log, I found "Caused by: java.io.IOException: Failed to read incoming message (not enough data). " Firstly I

Re: Data load is very slow in ignite 2.3 compare to ignite 1.9

HI Alexey, We have enough memory(around 48 GB) on server whereas allocation wise we are assigning/utilizing only 15GB memory. @Denis, I have tried all the configs given in mentioned link. But its not helping out. Thanks & regards Tejas On Thu, Dec 21, 2017 at 5:44 AM, Denis Magda

Re: Performance comparisons

Ignite community does not publish any performance benchmarks that compares Ignite to other projects and products. That's against ASF ideology. However, you can run benchmarks on your own following the doc below and we will be happy to assist if you believe final results look suspicious and more

Re: Ignite 2.3 Swap Path configuration is causing issue

Oh thanks Alexey, So if we are using ignite V2.X without enabling persistence and if data is spilling over the MaxSize. Then where will that data go ? On Thu, Dec 21, 2017 at 1:19 AM, Alexey Kukushkin wrote: > Swapping feature was removed in Ignite v.2 since native

Re: Ignite 2.3 Swap Path configuration is causing issue

Yes. Read more here: https://apacheignite.readme.io/docs/memory-configuration#section-data-regions — Denis > On Dec 20, 2017, at 8:24 PM, Tejashwa Kumar Verma > wrote: > > Oh thanks

Re: Data load is very slow in ignite 2.3 compare to ignite 1.9

Does it mean that you have 3 cluster nodes and all of them are running on a single server? Is data preloaded from a different machine? — Denis > On Dec 20, 2017, at 8:09 PM, Tejashwa Kumar Verma > wrote: > > HI Alexey, > > We have enough memory(around 48 GB) on

Re: Data load is very slow in ignite 2.3 compare to ignite 1.9

Hi Denis, I dont know that i got your question correctly or not. But still attempting to ans. For now i have 2 node cluster and both have 48-48 GB RAM available. And data is not Preloaded . Thanks & Regards Tejas On Thu, Dec 21, 2017 at 9:55 AM, Denis Magda wrote: > Does