Re: Failed to map SQL query

Hi, Most likely, the query intermediate result doesn't fit to JVM heap memory. The query may require all table data fetched before applying sorting. You can try to create a composite index over "act_id,mer_id,score" columns. On Tue, Aug 25, 2020 at 8:42 AM 1115098...@qq.com wrote: > Hi,an er

Re: Ignite IPv6 support

Hi, As far as I know Ignite can't work with IPv6 on Mac devices. Also, we have a ticket related to K8s with IPv6. The ticket had a patch and likely being fixed in one of future releases. Please, find known issues in jira [1]. Ignite is not tested well in IPv6 environment and any help here will be

Re: Fw:Expiry Policy can not working in gridgain 8.8.9

Hi, You wrote to the Apache Ignite user list. Apache Ignite and Gridgain are different projects with their own lifecycles and roadmaps. BTW, this looks like an issue in 8.8.9 that is already fixed in 8.8.18. Please contact the vendor for details.

Re: H2database dependency in Apache Ignite

Hi, Ignite uses H2 as one of 2 available execution engines. Module 'ignite-indexing' depends on H2. Long story short, we can't bump H2 version anymore as some integration points were dropped in higher H2 versions. However, this CVE along with other known issues[1] do not affect the Ignite. [1] ht

Re: H2 version security concern

Hi, Mentioned CVE has no affect Ignite. Please, see discussion on dev-list. http://apache-ignite-developers.2346864.n4.nabble.com/H2-license-and-vulnerabilities-td40417.html#a40418 On Wed, Dec 11, 2019 at 2:22 AM Evgenii Zhuravlev wrote: > Hi, > > There are plans to replace H2 with Calcite. Yo

Re: Geometry via SQL?

Hi, Please, refer to a Geo spatial index documentation [1] It is quite old, but should works. [1] https://apacheignite.readme.io/v1.7/docs/geospatial-queries#section-executing-geospatial-queries On Tue, Dec 10, 2019 at 10:57 PM richard.ows...@viasat.com < richard.ows...@viasat.com> wrote: > Is

Re: RE: Re: Unsafe usage of org.h2.util.JdbcUtils in Ignite

Hi, In Apache Ignite master branch I see a separate class H2JavaObjectSerializer that implements JavaObjectSerializer. Seems, this won't be released in 2.8 https://issues.apache.org/jira/browse/IGNITE-12609 On Thu, Mar 19, 2020 at 4:03 PM Andrey Davydov wrote: > Seem that refactor h2serilizer

Re: And again... Failed to get page IO instance (page content is corrupted)

ht-time > causes a catastrophe. > This mean no availability in fact - I had to clean data folders to start > my cluster after that > > BR, Oleksandr > > > On Fri, Jun 22, 2018 at 4:06 PM, Andrey Mashenkov < > andrey.mashen...@gmail.com> wrote: > >> Hi, >&

Re: And again... Failed to get page IO instance (page content is corrupted)

orked the code to get rid > of expiration policy. > All our non-persistent caches have expiration policy but this should not > be a problem, right? > > BR, Oleksandr > > On Thu, Jun 28, 2018 at 8:37 PM, Andrey Mashenkov < > andrey.mashen...@gmail.com> wrote: > >&g

Re: Query execution too slow

Hi, Composite index field order matters. Try to set order=3 for "value" column. On Tue, Aug 21, 2018 at 10:43 PM Ilya Kasnacheev wrote: > Hello! > > Yes, I am afraid that you will need another index. > > Regards, > > -- > Ilya Kasnacheev > > 2018-08-21 19:55 GMT+03:00 Prasad Bhalerao : > >> Hi,

Re: Slow SQL query uses only a single CPU

Hi, 1. Possible there are too much data should be looked for the query. With single node and parallelism=1 query will always run in single thread. You can try to add more nodes or increase query parallelism to utilize more CPU cores. 2. Index on date field may be not effective as reduce phase sh

Re: In the case of read-through cache, both Replicated and Partitioned mode are identical?

Hi, CacheStore semantic suppose you will warm-up a cache via calling cache.loadCache(). When you use read-through and forget load cache from back store then it is ok if no backups are updated on read operation. Backups and replicated cache in case of read-through just add some tolerance to node-l

Re: Slow SQL query uses only a single CPU

there a way to check what Ignite is actually doing? How are > indexs used (by Ignite or H2)? > > Cheers, > Eugene > > On Wed, Aug 22, 2018 at 3:54 AM, Andrey Mashenkov < > andrey.mashen...@gmail.com> wrote: > >> Hi, >> >> 1. Possible there are too m

Re: Slow SQL query uses only a single CPU

t; these flags and hints directly from SQL? >> >> From your description, it seems like the query is executed in the >> following order >> 1) Group by customer_id >> 2) For each group, perform the filtering on date using the index and >> aggregates >> &g

Re: Query 3x slower with index

Hi Actually, first query uses index on affinity key which looks more efficient than index on category_id column. The first query can process groups one by one and stream partial results from map phase to reduce phase as it use sorted index lookup, while second query should process full dataset on

Re: Query execution too long even after providing index

HI, Have you tried to increase index inlineSize? It is 10 bytes by default. Your indices uses simple value types (Java primitives) and all columns can be easily inlined. It should be enough to increase inlineSize up to 32 bytes (3 longs + 1 int = 3*(8 /*long*/ + 1/*type code*/) + (4/*int*/ + 1/*t

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 qry

Re: Apache Ingite Join returns wrong records

Hi, Try to use qry.setDistributedJoins(true). This should always return correct result. However, it has poor performance as due to intensive data exchange between nodes. By default, Ignite join only the data available locally on each node. Try to collocate your data to get better performance wit

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: http://apache-ignite-users

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 wit

Re: OVER() clause in ignite

Hi, Ignite have no support window functions due to lack of underlying H2. OVER is a part of SQL ANSI'03 standart, but Ignite claims to be ANSI'99 complaint. The only workaround is to rewrite query with using joins or calculate result manually. User aggregate functions also are not supported and w

Re: How could imporeve UNION ALL performance

Hi, Can you share a query plan? Do you have any indices on last and lastprice columns? Have you tried to run queries separately without Union? чт, 8 нояб. 2018 г., 23:47 wengyao04 wengya...@gmail.com: > Hi we use ignite as our searching backend. > Our cache is in replicated mode and primary_syn

Re: Cache Structure

Hi, Yes, to add a new item to a list value of second cache Ignite will have to deserialize whole list (with all it's items) then add new item and then serialize list again. You can try to use BinaryObjects to avoid unnecessary deserialization of list items [1]. Also note, k2 and k1 data will have

Re: Slow select distinct query on primary key

Yuri, how did you get inline size 60? I'd think 55 should be enough to inline Account_ID. 55 = 1 /* byte, type code */ + 4 /* int, array lenght */ + 50 /* data size for ANSI chars */ On Fri, Nov 30, 2018 at 1:25 PM Юрий wrote: > Please provide explain plan of the query to check that index is use

Re: SQL Query plan confusion

Hi, The difference in query plans is a 'bad' one use PUBLIC.TEST_DATA_K_V_ID index instead of PUBLIC.TEST_DATA_ID_K_V. Have you tries to remove other indices and left TEST_DATA_ID_K_V only? It looks weird for me, the 'good' query plan shows unicast requests as ID is affinity field, but 'bad' say

Re: Migrate from 2.6 to 2.7

Hi Andrey, It looks like you try to run "Select" sql query inside explicit transaction. Please, let us know if it is not true. This was workable in 2.7 as SQL had no transactional support and query just ignored transactional context (however "Select for Update" wasn't). For now, SQL Select query

Re: Text Query question

Hi, Unfortunatelly, it doesn't look as an open source solution. It is not clear how their Indices are integrated with Ignite page memory. If they do not use Ignite page memory then how they survive in failover scenarios as no shared test\test results are available? Otherwise, I bet they have head

Re: about https://github.com/amsokol/ignite-go-client

Hi, Ignite has no module ignite-go-client. Client you mentioned is not maintained by Apache Ignite community. AFAIK, we have no plans to add GO client support for now. Feel free to contribute. Usually, Apache Ignite is released twice a year. The latest version has been released at December 2018.

Re: java.lang.OutOfMemoryError: GC overhead limit exceeded

Hi, Most likely heap size is too low. Try to increase Xmx up to 4Gb or higher or avoid G1GC usage on small heaps as it is very sensitive to free heap memory. Looks like you have Visor node (or may be web-console) in grid. Is OOM happened only when Visor attached to grid? On Fri, Mar 1, 2019 at 7

Re: BinaryObject model replace() in client/server topology fails with ClassNotFoundFunction

; I know it is still early stage, usually how long it takes to fix this bug > and release a version because we need this functionality working for our > use case. > > On Sep 7, 2017 10:22 PM, "Andrey Mashenkov" > wrote: > > Hi, > Looks like a bug and CacheEntryP

Re: INSERT into SELECT from Ignite 1.9 or 2.0

Hi, Auto-increment fields are not supported yet. Here is a ticket for this [1] and you can track it's state. Moreover, underlying H2 doesn't support SELECT with JOINs nested into INSERT\UPDATE query. [1] https://issues.apache.org/jira/browse/IGNITE-5625 On Mon, Sep 18, 2017 at 12:31 PM, acet wr

Re: Join with subquery in 1.9 or 2.0

Hi, Looks like a bug. Would you please share a full stacktrace and a reproducer if possible? You can try to rewrite query without join to smth like this: Select .. from A, B Where A.id = B.id; On Mon, Sep 18, 2017 at 7:36 PM, acet wrote: > Hello, > I was looking to do something similar to: >

Re: INSERT into SELECT from Ignite 1.9 or 2.0

indeed are not supported for now though, it's true. > > - Alex > > 2017-09-18 16:09 GMT+03:00 Andrey Mashenkov : > > Hi, > > > > Auto-increment fields are not supported yet. Here is a ticket for this > [1] > > and you can track it's state. > >

Re: Fetched result use too much time

Lucky, 1. Looks like it make no sense to set query parallelism level higher number of available CPU on node. 2. Map query use index for field FASSIGCUID type of String and seems values are 16 chars length strings (32 bytes) By default, values with size < 10 bytes can be inlined in index, so Igni

Re: Join with subquery in 1.9 or 2.0

Hi, I can't reproduce the issue neither on 1.9 nor 2.0 nor 2.1 version. PFA repro attached. Would you please check if I've missed smth? On Wed, Sep 20, 2017 at 1:41 PM, Andrey Mashenkov < andrey.mashen...@gmail.com> wrote: > Hi, > > Looks like a bug. > >

Re: Cache Indexes not getting created Ignite v2.1

Hi, You mark field "name" with @QueryTextField and it can be used for TextQuery only. Looks like a bug that index type is missed in metatada. I'll check if it is so and fill a ticket. Field "name" should be annotated with @QuerySqlField(index = true) to allow SQL layer use this field in SQL query

Re: Ignite.NET 2.2 crashes on startup without any information

Hi Patrick, Would you please share ignite logs? On Fri, Sep 29, 2017 at 5:51 PM, Patrick Brunmayr < patrick.brunm...@kpibench.com> wrote: > Hello > > I am using Visual Studio 2017 and have installed Apache Ignite via NuGet. > Also checked the VC++ Redis is installed. > > Tried to run this little

Re: Services deployment constraining by cluster group not working

Hi Evgeniy, I've checked the code and found we use projection for services configured in node startup config, but we miss this for dynamic service deployment. By default, ignite.cluster().forServers() projection should be used, but in your case it is ignored too. I've created a ticket for this [

Re: Re: Fetched result use too much time

and there is a bug in queryParallelizm feature. Also I can find what ignite version you use. Would you try to switch to the latest one? On Tue, Oct 10, 2017 at 2:48 PM, Lucky wrote: > Andrey Mashenkov > Thank you very much! > 1.query parallelism:this will cause a problem: fe

Re: Local node was dropped from cluster due to network problems cascading failures

Hi, There is a known bug mixing IPv6 and IPv4 protocol can cause node failures. Try to set -Djava.net.preferIpv4Stack=true JVM option for all nodes. Also it is possible clients do smth that cause high GC pressure on server node. Would you please check GC logs? On Wed, Oct 11, 2017 at 12:14 PM, z

Re: Local node was dropped from cluster due to network problems cascading failures

Hi, Please find how to gather GC logs here [1]. [1] https://apacheignite.readme.io/docs/jvm-and-system-tuning#section-detailed-garbage-collection-stats On Wed, Oct 11, 2017 at 5:00 PM, zshamrock wrote: > Hi, Andrew. Thank you for the reply. > > We will definitely try this. > > Another thing we

Re: Ignite SQL function questions

Hi Ray, Ignite replaces H2 row object with its own stub. So, when you ask for a field value, ignite get entry represented by the row and get entry field according to configured mapping (via Queryentity [1] or via annotations [2]). Ignite stores data in serialized way, as every field can be accesse

Re: BackupFilter for the RendezvousAffinityFunction Questions

Hi Cris, 1. Just to clarify. Ignite use AffinityFunction for each cache (cache group from 2.1 [1]) to make 2 kind of mapping: key->partition and partitions->node. When we talk about data collocation (affinity collocation), we mean collocated data belongs to same partition. So, entries with same k

Re: Ignite cache transaction timeout

Hi, Transaction is timed out as transaction initiator node doen't receive response from other node in time by some reason. It may be due to an entry is locked by smbd or network issues or GC issues on other node or some bug. There is no starvation is stripe pool actually, as thread queue is empty

Re: Indexing fields of non-POJO cache values

Hi, There is no way to index such data as is. To index data you need to have entry_field<->column mapping configured. As a workaround here, leaves can be stored in cache as values. E.g. you can have a separate cache to index leaf nodes, where entries will have 2 fields: "original tree key" field

Re: Indexing fields of non-POJO cache values

Hi, Another way here is to implement your own query engine by extending IndexingSPI interface, which looks much more complicated. On Thu, Oct 12, 2017 at 4:23 PM, Andrey Mashenkov < andrey.mashen...@gmail.com> wrote: > Hi, > > There is no way to index such data as is. To index d

Re: How to cancel IgniteRunnale on remote node?

Hi, 1. Ignite.executorService() method return JDK ExecutorService interface implementation. 2. ExecutorService.shutdown() method javadoc says: * Initiates an orderly shutdown in which previously submitted * tasks are executed, but no new tasks will be accepted. * Invocation has no additional effec

Re: How to query to local partition cache data

Hi, setLocal - if true then query will be executed on local data node only. setCollocated - if true then rows are collocated on GROUP BY field and Ignite can evaluate aggregate functions on Map step. setDistributedJoins - if true then Ignite will try to join rows with rows on other nodes. Would y

Re: How the Ignite Service performance? When we test the CPU soon be occupied 100%

Hi aaron, Can you make and share JFR profile [1] if it is still actual? [1] https://apacheignite.readme.io/docs/jvm-and-system-tuning#section-flightrecorder-settings -- Best regards, Andrey V. Mashenkov

Re: How to cancel IgniteRunnale on remote node?

Hi James, Yes, Ignite will not cancel running Job if it is implement ComputeJobMasterLeaveAware and you can gracefully stop it. You need nothing to do, node will always receive topology changes events (e.g. NODE_LEFT). > Thanks a lot > Whether the Remote IgniteRunnable can be graceful shutdown

Re: heap dump on ignite servers

Hi Sumit, Sorry, for late answer. Yes. Possibly there is a memory leak in some cases on ignite-1.7. Try to switch to newer version. Please, ignore if it is not actual any more. -- Best regards, Andrey V. Mashenkov

Re: OutOfMemoryError

Hi Shuvendu, Looks like JVM can't allocate continuous memory buffer to serialize cache entry into byte array. Please, check if node has enough memory for it. On Tue, Oct 24, 2017 at 11:37 AM, shuvendu < shuvendu@travelcentrictechnology.com> wrote: > Hi, > > While pushing a huge array list

Re: Failed to query ignite

Hi, Looks like stacktrace is incomplete and it doesn't contains any reason why JdbcResponse has 'null' res field. Please, if connection string is correct (by default 10800 port should be used) and share full logs. Also, it is possible you close connection before results be retrieved from ResultSe

Re: Cannot activate Ignite with custom security plugin

Hi, Looks like a bug, GridRestProcessor doesn't supports CLUSTER_ACTIVE command. However, command is present in rest command list (see enum GridRestCommand code). I've created a ticket for this [1] [1] https://issues.apache.org/jira/browse/IGNITE-6741 On Tue, Oct 24, 2017 at 5:22 PM, calebs

Re: Hibernate Entity Cache Gets Stuck during GridCacheProxyImpl.put

Hi, Looks like thread is waiting for async transactional operation. Would you please share a full thread dump? There should be a thread in thread pool hanged or in progress. On Tue, Oct 17, 2017 at 12:31 PM, ksampath wrote: > Hi, > > *Environmental Details :* > ignite 2.2.0, Hibernate 4.3.0, J

Re: queryResult.getAll() stuck !!

Hi Sumit, What is version of Ignite do you use? Do you observe any CPU load? Would you please share query plan? You can get it via H2 console [1]. Do you create table via "CREATE TABLE" SQL command. It is possible, simple queries by PK are broken and full scan performed instead of using index in

Re: Ignite/Cassandra failing to use supplied value for where clause

Hi Kenan, Seems, column mapping is missed. You mix annotation configuration via @QuerySqlField annotation and creating table via "CREATE TABLE". I'm not sure it can work this way. Seems, you have neither QueryEntities configured nor IndexedTypes to Ignite can process annotations and know about id

Re: Retrieving keys very slow from a partitioned, no backup, no replicated cache

Hi Anand, Looks like a cluster wide operation cache.size() performed on every iteration. Please, take a look how to iterating over cache entries via ScanQuery [1] . [1] https://apacheignite.readme.io/v2.2/docs/cache-queries#scan-queries On Tue, Oct 24, 2017 at 7:40 PM, Anand Vijai wrote: > I h

Re: Failed to query ignite

Hi, Got it. Ignite has H2 in underneath. Try to use BIGINT as it should be mappe to java Long type. On Tue, Oct 24, 2017 at 9:54 PM, iostream wrote: > Hi Andrew, > > The result set was /null/ because the query failed in ignite. This is the > only stack trace printed. > > The problem occurs only

Re: Retrieving keys very slow from a partitioned, no backup, no replicated cache

Hi Anand, Sorry, I've mislooked you use scan query already. In your case you fetch data from grid and then try to make invoke for every batch of entries. I doubt invokeAll will give any speedup in this case comparing to simple put as you already have full value fetched in your hands. Why you won'

Re: Cannot activate Ignite with custom security plugin

Oh, you are right. It looks already fixed. On Tue, Oct 24, 2017 at 9:12 PM, calebs wrote: > I just checked out ignite-2.3 branch, and I'm gladly surprised to see the > following two cases are already included in the GridRestProcessor.authorize > method. > > case CLUSTER_ACTIVE: >

Re: Ignite/Cassandra failing to use supplied value for where clause

Kenan, You can try to set IndexedType pair to cache configuration [1] to force Ignite process annotations on Key\Value classes. [1] https://apacheignite.readme.io/docs/indexes#section-registering-indexed-types On Tue, Oct 24, 2017 at 11:00 PM, Kenan Dalley wrote: > These were included in the p

Re: Ignite-cassandra module issue

Hi Tobias, What ignite version do you use? May be this was already fixed in latest one? I see related fix inclueded in upcoming 2.3 version. See IGNITE-5897 [1] issue. It is unobvious, but this fix session init\end logic, so session should be closed in proper way. [1] https://issues.apache.org/j

Re: Hammering Cassandra with Ignite seems to get ignite into an infinite loop

Tobias, Looks it is a duplicate. I've answered in next tread: http://apache-ignite-users.70518.x6.nabble.com/Ignite-cassandra-module-issue-td13808.html You can try to build Ignite from master [1] or ignite-2.3 [2] branch and check against it and let us know if the issue will gone or not. [1] h

Re: when client node connect to server node, server node throws NotSerializableException

Hi, Looks like node fails while trying to serialize cache configuration. Would you please check if com.pingan.pilot.cache.impl.ignite. PIgniteCacheStoreFactory implements Serializable? On Wed, Oct 25, 2017 at 10:12 AM, Jeff Jiao wrote: > Hi Ignite Community, > > I have a Ignite server node run

Re: Failed to query ignite

Hi, Looks like a bug. Can you share a simple repro? So, it can be easily checked against master or ignite-2.3 branch if it is already fixed or a ticket should be created. On Wed, Oct 25, 2017 at 5:28 PM, iostream wrote: > I think i have found the problem here. When I query my cache on the P

Re: Ignite/Cassandra failing to use supplied value for where clause

Kenan, I've found there is an issue that can cause unexpected behavior when using Cassandra keyPersistence configuration with Ignite annotations [1]. But XML way should work. I'm confused as in first message you wrote Test1Key has 'id' field, in last message it has 'my_id' field and 'myId' in map

Re: Re: insert data took too much time

Hi Lucky, Also you can try to remove indices from configuration and create them dynamically via "CREATE INDEX" sql query after load finished. On Thu, Oct 12, 2017 at 10:36 AM, Lucky wrote: > afedotov > Thanks a lot ! > > It took 25 seconds with cache.putAll performance. this is better t

Re: Query performance against table with/out backup

Hi, You wrote you use persistence=enabled. Looks like you try to start cache with changed (backup=2) configuration without recreating the cache, grid restore cache from store with its config and doesn't apply a new one. Looks weird that neither new number of backups wasn't applied nor error occur

Re: Failed to query ignite

Hi, Thanks for reproducer. I've make some changes and run test against 2.1, 2.2 and 2.3 version. Test with affinity key fails on 2.1 and 2.2 versions and looks ok on 2.3 version. Seems, there was a bug in 2.1 and it is already fixed in 2.3. PFA repro. On Thu, Oct 26, 2017 at 10:39 AM, iostream

Re: Ignite log

Hi, Would you please attach full log as partial screenshot attaches is not informative? On Fri, Oct 27, 2017 at 12:33 PM, deleerhai <185961...@qq.com> wrote: > hello! > > Following the launch of the ignite has been following the log output, what > is the reason? Why is there a timeout? >

Re: Incorrect map query built when joining with a subquery with group by statement

Hi Alin, Ignite have no support for non-collocated subqueries [1] [2], here is a ticket [3]. Try to set collocated flag to true [4] to hint Ignite your query is collocated. [1] http://apache-ignite-users.70518.x6.nabble.com/Does-Ignite-support-nested-SQL-Queries-td1714.html [2] http://apache-ign

Re: when client node connect to server node, server node throws NotSerializableException

Hi Jeff, Looks weird. Can you share a StoreFactory code and cache config? Is factory stateless? Or may be there is smth else not stateless in cache configuration that is missed in log? On Fri, Oct 27, 2017 at 10:50 AM, Jeff Jiao wrote: > hi guys, > > can anyone give some advice... > what can y

Re: cache closed or destroyed issue

Hi, Seems, you start ignite in some bean that has dies by some reason and your cache proxy become obsolete. Can you share logs? On Fri, Oct 27, 2017 at 3:03 AM, Pradeep Badiger wrote: > Hi, > > > > We are facing an issue with Ignite cache where it throws an > IllegalArgumentException with Cache

Re: Query performance against table with/out backup

Hi blackfield, I can't reproduce the issue with changing number of backups when cache was re-created. On Fri, Oct 27, 2017 at 8:45 PM, blackfield wrote: > @Andrew Mashenkov, I notice that you opened IGNITE-6781. > However, I actually destroyed the original cache with backup == 1, recreate > a

Re: How can I get Ignite security plugin to work with JDBC thin client?

Hi Caleb, JDBC thin client have no support security plugin for now. If you don't need full permissions support for sql objects (i mean "GRANT" operation), but just restrict unauthorized access to grid, then you can wait for IGNITE-6625 [1] and try JDBC via SSL. [1] https://issues.apache.org/jir

Re: Exception in calculating cache size

Hi, This is known bug that transformer applies only to first page of results. Here is a ticket [1] [1] https://issues.apache.org/jira/browse/IGNITE-5804 On Sat, Oct 28, 2017 at 8:57 AM, naresh.goty wrote: > Hi All, > > We are seeing an issue with calculating size of few caches in our > applic

Re: Exception in calculating cache size

int cnt=0; while(curs.hasNext()){ cnt += ((CompositeEntity)entry.getValue()).size() } return cnt; } } ); On Mon, Oct 30, 2017 at 4:38 PM, Andrey Mashenkov < andrey.mashen...@gma

Re: Exception in calculating cache size

Dmitry, Yes, you are right. we should broadcast a job with local scan queries. On Mon, Oct 30, 2017 at 4:54 PM, Dmitry Pavlov wrote: > Hi Andrey, should we limit scan query to be executed only for current node > here with setLocal() method? > > > пн, 30 окт. 2017 г. в 16:48, A

Re: Renentrant Lock & deadlock

Hi Rajiv, Seems, it is same issue as IGNITE-6380. I see tread blocks on dynamic cache for ignite datastructures creation. [1] https://issues.apache.org/jira/browse/IGNITE-6380 On Sat, Oct 28, 2017 at 12:15 AM, rajivgandhi wrote: > Hi, > In line with a deadlock reported earlier >

Re: How can I get Ignite security plugin to work with JDBC thin client?

Hi, IgniteCache.query() method requires CACHE_READ permission, but looks like all JDBC clients bypass security checks. On Mon, Oct 30, 2017 at 5:27 PM, calebs wrote: > Hi Andrew, > > Then, does JDBC "thick" client have the support security plugin? The > security includes User Authentication and

Re: Estimation of cluster effective capacity

Hi, It is very rough estimations. 1. Recommended minimal heap size for server node is 512Mb. If you plan to retrieve large dataset with getAll or some queries with large page size, you should bother with requested data will fit in memory. Also JVM GarbageCollector feels much better if there is 15

Re: Quick questions on replication and write synchronization mode

Hi, Read requests by default goes to PRIMARY node until readFromBackup is true that allow to read local backup data. Write requests always applies on PRIMARY node first then primary node send request to backup nodes. The main difference between FULL and PRIMARY sync modes is that with second write

Re: when client node connect to server node, server node throws NotSerializableException

Hi Jeff, Is BoConverter object serializable and is class present on all nodes? You store configured with storeKeepBinary true, so store will receive binary objects. Why you need value class here? Binary object concept is to overcome a requirement to have all value classes on server side. On Tu

Re: How can I get Ignite security plugin to work with JDBC thin client?

Caleb, I've found authorization should work only when you use url like "jdbc:ignite://" with thick driver, and won't if "jdbc:ignite:cfg://" is used. On Tue, Oct 31, 2017 at 4:33 PM, calebs wrote: > The javadoc for the jdbc thick client states that property: > "ignite.client.credentials" is av

Re: when client node connect to server node, server node throws NotSerializableException

Hi Jeff, CacheStore class should be in classpath on all nodes including clients. 1 нояб. 2017 г. 4:52 пользователь "Jeff Jiao" написал: > Hi Andrew, > > Thanks a lot for all the replies. > > yes BoConverter implements Serializable, or Ignite will throw > NotSerializableException. > The "Class"

Re: Ignite Nodes not connecting to cluster in docker swam mode

Hi Rishi, Check if port 31100 is reachable. Also it is possible you have outdated linux kernel with a bug that return error instead of dropping a packet [1] e.g. network buffer is full. Can you try to start a grid on newer linux\kernel version? [1] https://github.com/playframework/play-plugins/is

Re: Ignite/Cassandra failing to use supplied value for where clause

Hi Kenan, Looks like annotation configuration is not allowed together with xml comfiguration. I wonder there was no Exception. I've made an example with all mapping configured in xml and got no errors. Please, check an example that workable for me [1]. [1] https://github.com/AMashenkov/ignite-w

Re: Ignite/Cassandra failing to use supplied value for where clause

Got it. Seems, CassandraStore doesn't supports storeKeepBinary(true) flag. On Wed, Nov 1, 2017 at 8:04 PM, Andrey Mashenkov wrote: > Hi Kenan, > > Looks like annotation configuration is not allowed together with xml > comfiguration. > I wonder there was no Exception. I

Re: Deadlock detected while accessing caches

Hi Amit, Do you use getAll, putAll or invokeAll on non-sorted keysets? On Thu, Nov 2, 2017 at 9:43 PM, Amit Pundir wrote: > Hi, > I have a Ignite 2.0 cluster of 8 servers and 8 clients. It has 6 caches > which are transactional and partitioned. > I use pessimistic transactions with a timeout o

Re: ignite web agent still has "monitoring" tab?

Hi, Ignite web console never has "monitoring tab". On Thu, Nov 2, 2017 at 9:31 PM, sherryhw wrote: > t1372/2017-11-02_14-29-18.png> > > Hi I am new to Ignite web agent. I deployed the web console on the server > and I dont find "monitorin

Re: Threads waiting

Hi, Your thread is waiting for partition exchange that possibly hangs due to some reason. Is it possible, to share logs and thread dumps at a time when you observed hanging? On Sun, Oct 29, 2017 at 4:09 AM, naresh.goty wrote: > Hi, > > We are seeing threads blocked when reading (only reads not

Re: Affinity Compute latency

Hi, Most likely, first compute call will register a job class and it takes most of time. Make sure your class will not be unloaded between compute calls [1]. Try to make much more cycles to benchmark to make it run a few tens of seconds and add warm-up cycles. You can see how it done in Ignite ya

Re: Ignite Affinity Latency

Answered in [1] thread. [1] http://apache-ignite-users.70518.x6.nabble.com/Affinity-Compute-latency-tt18028.html On Wed, Nov 8, 2017 at 9:03 AM, rajivgandhi wrote: > Hi, > We are seeing higher latency form ignite affinity (single key)/compute > (multiple keys) of 7ms compared to get/getall 700

Re: Cache Mode = LOCAL throwing exception while initialisation

Hi Ankit, It is a known bug. Here is a ticket for it IGNITE-6794 [1]. A s a workaround you can set empty MemoryConfiguration on client. [1] https://issues.apache.org/jira/browse/IGNITE-6794 On Thu, Nov 9, 2017 at 2:46 PM, Ankit Singhai wrote: > Hi, > I am trying to create an Ignite cache with

Re: Ignite Nodes not connecting to cluster in docker swam mode

Hi, How many nodes you have? For large grids, there is a recommendation to prestart one node and then start others. Would you please share grid configuration and thread dumps from stucked nodes? On Thu, Nov 2, 2017 at 11:52 AM, rishi007bansod wrote: > Hi, > Initially I was trying with auto

Re: Renentrant Lock & deadlock

Hi, ignite.reentrantLock() creates a cache for datastructures dynamically if is not exists yet. So, both it is same issue. On Tue, Oct 31, 2017 at 7:15 PM, rajivgandhi wrote: > That one was with ignite.getOrCreate > This one is with ignite.reentractLock. > > Are the both due to the same defect?

Re: Deadlock detected while accessing caches

Hi dark, It is known issue. The only workaround here is to presort keys before getAll \ putAll. On Fri, Nov 3, 2017 at 10:05 PM, dark wrote: > I also experienced a deadlock while attempting putAll using a HashMap. > I used AtomicityMode as ATOMIC. > If you are like me, the following process mig

Re: Deadlock detected while accessing caches

Hi Amit, Transactions on unsorted keysets also can cause a deadlock. However, unlikely to getAll on Atimoc cache, Ignite should detect deadlock in transactions. On Thu, Nov 9, 2017 at 3:31 PM, Andrey Mashenkov wrote: > Hi dark, > > It is known issue. The only workaround here is to pre

Re: Ignite/Cassandra failing to use supplied value for where clause

I can't reproduce the issue. Is it possible you try to get value for key with 'null' id field? On Fri, Nov 3, 2017 at 5:28 AM, Kenan Dalley wrote: > Hi Andrey, > > I tried taking pieces from your example and I still couldn't make it work. > First, I removed the annotations out of the POJOs and p

  1   2   3   4   5   6   >