Re: Ignite Query Slow

Discovery is a basic functionality, that is needed for clustering. You can try to implement your own DiscoverySpi, which will do absolutely nothing, but do you really want it? вт, 11 дек. 2018 г. в 13:42, Skollur : > is there anyway i can run ignite on machine and port without discovery? > > > >

Re: Ignite Query Slow

is there anyway i can run ignite on machine and port without discovery? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite Query Slow

Port 10800 is used by Ignite for thin clients by default, looks like it was bound earlier on this machine. But why do you want to use 10800 for discovery? вт, 11 дек. 2018 г. в 13:09, Skollur : > It is different machine. Wondering why not able to use same port? I have > put > the IP and port for

Re: Ignite Query Slow

It is different machine. Wondering why not able to use same port? I have put the IP and port for each node in different machine. Machine 1: node discovery.setLocalAddress("192.2.2.1"); discovery.setLocalPort(new Integer("10800"))); Machine 2: node discovery.setLocalAddress("192.2.2.2");

Re: Ignite Query Slow

There is also a portRange property, which is set to 100 by default. If the first address is already occupied, then discovery will try to bind to the next one. вт, 11 дек. 2018 г. в 12:14, Skollur : > I have following code in node1 -> > TcpDiscoverySpi discovery = new TcpDiscoverySpi(); >

Re: Ignite Query Slow

I have following code in node1 -> TcpDiscoverySpi discovery = new TcpDiscoverySpi(); discovery.setLocalAddress("192.2.2.1"); discovery.setLocalPort(new Integer("10800"))); cfg.setDiscoverySpi(discovery); and node 2 -> TcpDiscoverySpi discovery = new

Re: Ignite Query Slow

In case, when you have replicated cache and you connected with thin client only to one of them, it decides that it can perform query on the one node only, because all data can be found locally. You can try to connect a different client to the different node and divide all queries into 2 clients.

Re: Ignite Query Slow

sql-performance.PNG enclosed sql performance time. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite Query Slow

Ok..Will 2 nodes helps? I saw only one node is busy most of time since I have configured as REPLICATE and also found that REPLICATE is faster in multi join queries than PARTITIONED in my case. Is there anyway REPLICATE (with 2 nodes) take loads equally among 2 nodes? -- Sent from:

Re: Ignite Query Slow

It should be better, I'd recommend using the default value - it will be calculated based on the cores count. пн, 10 дек. 2018 г. в 10:56, Skollur : > How about 6 cores. Will that help? In that case what is the thread counts? > > > > > -- > Sent from:

Re: Ignite Query Slow

How about 6 cores. Will that help? In that case what is the thread counts? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite Query Slow

2 cores are just not enough for 100 running simultaneously queries, of course, you will see a lot of context-switching, which will lead to the slowness of the part of queries. пн, 10 дек. 2018 г. в 10:35, Skollur : > Enclosed CPU/Thread usage. Ignite became super slow after applying > below.

Re: Ignite Query Slow

Enclosed CPU/Thread usage. Ignite became super slow after applying below. I am still not sure how many threads are required to span 100 queries simultaneously. I am seeing CPU is hitting almost 100%. cfg.setQueryThreadPoolSize(16); cfg.setSystemThreadPoolSize(16);

Re: Ignite Query Slow

Thank you for reply. I have 2 core, 20 GB memory space allocated for Ignite cache. My data size is about 3 to 4 GB. I have batch process(multi threaded) where simultaneously 100 requests sends to ignite cache (same query with different parameters for each request). What is the recommended thread

Re: Ignite Query Slow

Currently I have only one node and other node is idle and brought it down. I have noticed that only one node is busy and I have code as below. IgniteConfiguration cfg = new IgniteConfiguration(); TcpDiscoverySpi discovery = new TcpDiscoverySpi();

Re: Ignite Query Slow

do you have gc logs from an another node? вт, 4 дек. 2018 г. в 12:14, Skollur : > Ignite.zip > > Ignite is using high CPU and enclosed high CPU profile. Let me know if you > need any further information to help us on this. >

Re: Ignite Query Slow

Ignite.zip Ignite is using high CPU and enclosed high CPU profile. Let me know if you need any further information to help us on this. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite Query Slow

Attached. Thanks gclog.zip -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite Query Slow

Can you attach it instead of just posting to the message? пн, 26 нояб. 2018 г. в 10:12, Skollur : > Also attached GC-> > > 2018-11-26T13:35:23.058-0500: 1172.703: [GC pause (G1 Evacuation Pause) > (young), 0.0070730 secs] >[Parallel Time: 6.3 ms, GC Workers: 2] > [GC Worker Start (ms):

Re: Ignite Query Slow

Also attached GC-> 2018-11-26T13:35:23.058-0500: 1172.703: [GC pause (G1 Evacuation Pause) (young), 0.0070730 secs] [Parallel Time: 6.3 ms, GC Workers: 2] [GC Worker Start (ms): Min: 1172702.9, Avg: 1172703.3, Max: 1172703.7, Diff: 0.8] [Ext Root Scanning (ms): Min: 1.1, Avg: 1.4,

Re: Ignite Query Slow

Hello Are u suggesting to have more nodes with REPLICATE OR PARTITIONED settings? Thanks -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite Query Slow

Hello, It is hard to tell what is the bottleneck in your case, could be anything. I suggest tracking CPU and memory usage, enable GC logs. Adding more nodes will definitely help in this case. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite Query Slow

Hi, >From your description, it looks like it could be a long GC pause. How much heap do you have? Can you collect GC logs from analysis? Evgenii пт, 23 нояб. 2018 г. в 22:02, Skollur : > Hello > > I have ignite server running with 2 nodes. Each node has 30 cache stores > with one table in each

RE: Ignite Query Slow

Any help on this? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

RE: Ignite Query Slow

Thank you..Tried @QuerySQLFields...but column name not appeared same as database table(i.e underscore("_") is missing in ignite). Hence I have added index to qryEntity and noticed that Query takes about 7 seconds (i.e select * from customercache.customer) for against ignite cache data of 200,000

RE: Ignite Query Slow

; @QuerySqlField(index = true) private int age; } then the call setIndexedTypes(Long.class, Person.class) will create indexes for both `name` and `age`. Thanks, Stan From: Skollur Sent: 2 октября 2018 г. 16:51 To: user@ignite.apache.org Subject: Re: Ignite Query Slow

Re: Ignite Query Slow

Documentation has example as ccfg.setIndexedTypes(Long.class, Person.class);. I believe this is single field. How to register multiple indexes for CacheConfiguration? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite Query Slow

Hi, Ignite provides 2 way for configuring indices: queryEntity and annotation based. Seems, you either forget to setIndesTypes or tring mix both of these approaches. Please, find examples in documentation available via link I've provided earlier. пн, 1 окт. 2018 г., 18:05 Skollur : > I tried

Re: Ignite Query Slow

I tried with setting up field with @QuerySqlField (index = true) and still slow. Example : /** Value for customerId. */ @QuerySqlField (index = true) private Long customerId -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite Query Slow

Please take a look at this. https://apacheignite.readme.io/v2.6/docs/indexes#section-queryentity-based-configuration 29 сент. 2018 г. 3:41 пользователь "Skollur" написал: Thank you for suggestion. Can you give example how to create secondary indices? -- Sent from:

Re: Ignite Query Slow

Thank you for suggestion. Can you give example how to create secondary indices? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite Query Slow

Hi, Please, try to create secondary indices on join columns, otherwise query will fall into full table scan. Then if you will see SCANs, as next step, you can try to rewrite your query with different tables join order. Sometimes, underline H2 can change join order to non optimal. In that case

Re: Ignite Query Slow

Here is the explain query # PLAN 1 "SELECT ADDR__Z2.ADDRESS_LINE_1 AS __C0_0, ADDR__Z2.ADDRESS_LINE_2 AS __C0_1, ADDR__Z2.ADDRESS_LINE_3 AS __C0_2, ADDR__Z2.STREET AS __C0_3, ADDR__Z2.CITY AS __C0_4, ADDR__Z2.STATE AS __C0_5, ADDR__Z2.COUNTRY AS __C0_6,

Re: Ignite Query Slow

1. I have defined primary key - dwId 2. Not defined affinity_key since there is no Forgein Key in table. 3. CacheConfiguration ccfg = new CacheConfiguration(); ccfg.setName(cacheName); ccfg.setCacheMode(CacheMode.PARTITIONED);