Re: Improving Get operation performance

Victor, Then, I would recommend to check if you have a swapping enabled in OS. If you have only 75gb on the machine and you started 3 nodes with 14 gb off heap and something like a 16gb heap each, probably OS started a swapping process, which will affect a performance. Additionally, there is no n

Re: Improving Get operation performance

Hi Viktor, It looks like you're running 3 server nodes on the same physical machine, right? How do you run Cassandra benchmarks? Do you use the same 2 machines? How many Cassandra instances do you have? Also, how much memory do you have on this machine? Best Regards, Evgenii ср, 27 нояб. 2019 г

Re: Ignite singel instance

Hi, Do you use only one ODBC client? Can you start one more ODBC client and check the performance? Thanks, Evgenii сб, 2 нояб. 2019 г. в 16:47, Siew Wai Yow : > Hi, > > We are doing POC on ignite performance using ODBC driver but the > performance is always capped at around 1700 TPS which is to

Re: Query Parallelism through SQL

Hi, When you create table using DDL, you can choose template with a cache configuration(CREATE TABLE WITH TEMPLATE): https://www.gridgain.com/docs/latest/sql-reference/ddl#create-table Inside template you can define query parallelism Evgenii чт, 17 окт. 2019 г. в 09:11, Kurt Semba : >

Re: ClassCastException retrieving cached object

Hi, Peer class loading doesn't work with model classes, more information regarding use cases for peerClassLoading can be found here: https://www.gridgain.com/docs/latest/developers-guide/peer-class-loading Evgenii вс, 6 окт. 2019 г. в 04:09, niamin : > Working with Ignite 2.7.6 using spring co

Re: Map Reduce over cache items, where values are sequences

For example, query with partition will look like : QueryCursor> qry = cache.query(new ScanQuery().setPartition(part)); вт, 1 окт. 2019 г. в 15:25, Evgenii Zhuravlev : > Hi, > > To parallelise everything properly, I would recommend starting an > affinityCallable per pa

Re: Map Reduce over cache items, where values are sequences

Hi, To parallelise everything properly, I would recommend starting an affinityCallable per partition(1024 by default). Inside this compute job, you can collect information for the certain partition only using ScanQuery(or SQLQuery) пт, 27 сент. 2019 г. в 18:09, Stas Girkin : > Hello everyone, >

Re: Ignite bulk data load issue

each node > > > > > > *Regards,* > > *Favas * > > > > *From:* Evgenii Zhuravlev > *Sent:* Tuesday, September 24, 2019 12:44 PM > *To:* user@ignite.apache.org > *Subject:* Re: Ignite bulk data load issue > > > > Hi, > > > > Looks

Re: Huge number of .classname files

Hi, These files are mainly used for reconnection purposes, so after it client node have everything needed. You can clear it if you want, it shouldn't affect the node. Evgenii вт, 24 сент. 2019 г. в 14:53, BOUCHRIT Abderrahmane : > Hi All, > I have an Ignite 2.6.0 cluster and my application is

Re: Ignite bulk data load issue

Hi, Looks like you can have really slow disks. What kind of disk do you have there? I see throttling in logs, Because the write operation is really slow. Evgenii пн, 23 сент. 2019 г. в 13:07, Muhammed Favas < favas.muham...@expeedsoftware.com>: > Hi, > > > > I need help to figure out the issues

Re: distributed sql join not working as mentioned in documentation

Hi, To make work this query, you can add one where clause or join condition in the query, for example: where c.id = city_id;. I don't really understand why do you want to run a fully distributed cross join on these tables - it doesn't make sense, moreover, it will lead to the a lot of data movemen

Re: Server Nodes Stopped Unexpectedly

est any tool? > > 4) I understand that node gets segmented because of long GC pause or > network connectivity. Is my understanding correct? > > 5) What is the purpose of networkTimeout configuration? In my case it is > set to 1 . > > Regards, > Akash > > On Mon, Jul 29,

Re: Rebalancing only to backups

Hi Abhishek, That's how it works now if you have enabled Persistence. Actually, that's the main reason why BaselineTopology was introduced - we don't want to move a lot of data between nodes if we know that node will return soon after a failure: https://apacheignite.readme.io/docs/baseline-topolog

Re: exceptions in Ignite node when a thin client process ends

Hi, This message is absolutely unharmful, however, I agree that server node shouldn't print this exception since nothing wrong happened there. I've created a ticket in Jira for fixing this behavior: https://issues.apache.org/jira/browse/IGNITE-12032 Evgenii чт, 1 авг. 2019 г. в 09:33, Matan Lev

Re: Server Nodes Stopped Unexpectedly

ssue happens. > But in this case multiple JVMs were terminated.Can it be a bug in Ignite > 2.6 version? > > Thanks, > Akash > > On Fri, Jul 26, 2019 at 4:00 PM Evgenii Zhuravlev < > e.zhuravlev...@gmail.com> wrote: > >> I don't see any specific error

Re: Server Nodes Stopped Unexpectedly

t; > On Wed, Jul 24, 2019 at 12:04 PM Akash Shinde > wrote: > >> Hi, >> Please find attached logs from all server and client nodes.Also attached >> gc logs for each node. >> >> Thanks, >> Akash >> >> >> On Tue, Jul 23, 2019 at 8:59 PM Evge

Re: Server Nodes Stopped Unexpectedly

Hi, Can you please share full logs from the node start from all nodes in the cluster? Thanks, Evgenii вт, 23 июл. 2019 г. в 16:51, Akash Shinde : > I am using Ignite 2.6 version. I have created a cluster of 7 server nodes > and three client nodes. Out of seven nodes five nodes stopped unexpect

Re: too many dirty pages

Hi, It's not a warning, it's just an INFO message about writing checkpoint to the disk. The reason for this checkpoint was that there were "too many dirty pages". Here is how Ignite persistence works: https://cwiki.apache.org/confluence/display/IGNITE/Ignite+Persistent+Store+-+under+the+hood Best

Re: Ignite Rest API is not working

There is a chance that port 8080 was busy and it was bound to the next port. I'd recommend checking Ignite logs to make sure that rest was started and check the port. Evgenii пт, 14 июн. 2019 г. в 19:47, Kishan : > I want to use REST API provided by ignite. > > I have downloaded the ignite binar

Re: Ignite Nodes Go Down - org.apache.spark.rpc.RpcTimeoutException: Futures timed out after [10 seconds]. This timeout is controlled by spark.executor.heartbeatInterval

Hi, > we have noticed that Ignite nodes are not responding in the heart beat interval time and hence the re-balancing of data is happening and followed by query cancellation. It looks like a long GC pauses for me. Can you share full logs from all the nodes? As the fast workaround, I can suggest i

Re: cache.destroy() vs cache.close()

Hi, Cache.destroy() completely removes caches from all the nodes in the cluster, while Cache.close() just closes the local proxy for the cache. So, yes, data will be lost in case of invoking destroy from the client node. Evgenii пн, 10 июн. 2019 г. в 19:23, foobar2 : > Hello. I am using Ignite

Re: [data-streamer-stripe-2-#35][] Critical system error detected.

Hi, Here is the documentation regarding this message: https://apacheignite.readme.io/v2.7/docs/jvm-and-system-tuning#section-file-descriptors Evgenii вт, 7 мая 2019 г. в 12:09, yangjiajun <1371549...@qq.com>: > thread_dump.rar >

Re: Issues with Clients joining cluster on Kubernetes (EKS)

Yes, I know that users have deployments in kubernetes and they don't have any issues with that. Did you follow this instruction: https://apacheignite.readme.io/docs/kubernetes-deployment ? Please make sure that ports for Discovery and Communication are open in this environment. Evgenii пт, 3 мая

Re: Failed to archive WAL segment

Hi, How many folders you have in /opt/ignite/wal/ ? Is there a chance that you have there 2 folders with different node IDs? Can you share your configuration? Thanks, Evgenii пн, 29 апр. 2019 г. в 11:17, shivakumar : > HI all, > > I have 7 node ignite cluster running on kubernetes platform, eac

Re: Issues with Clients joining cluster on Kubernetes (EKS)

Why there is no lines in the server log between these two: [17:10:48,827][INFO][sys-#149][GridCachePartitionExchangeManager] Sending Full Message for AffinityTopologyVersion [topVer=10, minorTopVer=1] performed in 1 ms. [19:39:58,910][INFO][disco-event-worker-#62][GridDiscoveryManager] Added new n

Re: Creating off-heap REPLICATED cache with Eviction policies borks the cluster.

Yes, I tried to do this and it works. Just delete folder work/db/node-NODEID/CACHE_NAME. Also, I created a ticket for adding validation for this situation: https://issues.apache.org/jira/browse/IGNITE-11832 Evgenii пт, 3 мая 2019 г. в 13:39, Evgenii Zhuravlev : > Hi > > I believe tha

Re: How data region is propagated to other nodes

Data regions can't be created dynamically, because it's needed to preallocate memory. I believe that in your use case you can just create it statically on cluster start, is there a problem with that? Evgenii пт, 3 мая 2019 г. в 12:54, dhiman_nikhil : > Can I create data regions on All Servers dy

Re: Creating off-heap REPLICATED cache with Eviction policies borks the cluster.

Hi I believe that you can just remove folder related to the newly created cache, have you tried to do this? Evgenii чт, 2 мая 2019 г. в 23:15, John Smith : > Hi running 2.7.0, > > I have a 4 node cluster running with off-heap persistence works great! > > I then by mistake tried to create a REPL

Re: How data region is propagated to other nodes

Then you can simply create 2 different data regions for all server nodes in the cluster - one with persistence and one without. After that, you can decide, how you want to store your key - with persistence or without. Evgenii пт, 3 мая 2019 г. в 08:27, dhiman_nikhil : > As per documentation, I c

Re: How data region is propagated to other nodes

Hi, No, Data region configuration won't be propagated to other nodes in the cluster. DataRegion is only a local configuration, so, you have to configure it on each node. Moreover, these the same data region on different nodes can have different maxSize, which could be useful in case of using NodeF

Re: Transactions from Python

Hi Stéphane Community is working on this functionality at the moment, here you can find design document and discussion regarding this feature: https://cwiki.apache.org/confluence/display/IGNITE/IEP-34+Thin+client%3A+transactions+support Alternatively, you can start to use ODBC from python, now SQ

Re: sizing

Hi, What do you mean here? Do you mean binary fields VS varchars? Could you please give an example of the object? Thank you, Evgenii вт, 30 апр. 2019 г. в 12:27, Clay Teahouse : > Hi All > If I choose binary data type for my objects, as opposed to varchar, will > it result in any saving, and ye

Re: Issues with Clients joining cluster on Kubernetes (EKS)

Hi, I see this warning in the logs: Local node's value of 'java.net.preferIPv4Stack' system property differs from remote node's (all nodes in topology should have identical value) [locPreferIpV4=true, rmtPreferIpV4=null, locId8=20c2dc57, rmtId8=699d2d8c, rmtAddrs=[ignite-jwp-0.ignite.ignite-jwp.s

Re: Ignite DataStreamer Memory Problems

Hi, Lucene indexes are stored in the heap, while I see that in reproducer you've limited heap size to 1gb. Are you sure that you used these JVM opts? Can you please share logs from your run, so I can check the heap usage? Best Regards, Evgenii вт, 30 апр. 2019 г. в 00:23, kellan : > The issue s

Re: Older client connections to Ignite blocking new clients

Hi, Could you provide logs from all the nodes, including servers and clients? Evgenii пт, 26 апр. 2019 г. в 11:04, mahesh76private : > Hi, > > We are experiencing a strange issue on ignite 2.7 for a few months now. > > we have 4 ignite clients (say GROUP1) connected to a ignite cluster > native

Re: Failover in thin client mode

Hi, I believe that this paragraph describes what you want to see: Updating partition mapping It is important for client to keep partition mapping updated. To ensure this, the following changes are proposed: 1. Changes in Standard Message Response header. It is proposed to add flag to every

Re: critical thread has been detected

Could you share logs from client nodes? I believe we can find more useful information there. Also, could you share a full log file, not a console output? Or, alternatively, you can run Ignite with -DIGNITE_QUIET=false to enable INFO logging for console output. Evgenii чт, 25 апр. 2019 г. в 00:19,

Re: write behind not working for RDBMS

Hi, writeThrough property enables cache store integration overall, while writeBehindEnabled property controls whether store updates are async or not. So this is correct behavior. Evgenii вт, 2 апр. 2019 г. в 00:24, himanshu : > Hi, > > I am using ignite 2.7.0, when I am trying to test write thr

Re: SQLLine: Insert into for complex object not working

Hi, Looks like you're trying to insert the entry with the same key as before. SQL INSERT command doesn't allow to do that(in all DBs). Looks like you need to use UPDATE or UPSERT commands Evgenii вт, 2 апр. 2019 г. в 10:43, ashishb888 : > I have a cache, with complex key (3 fields). I am able g

Re: Ignite 2.7 Client node security credentials configuration

Hi, When you use the thick client, it uses pretty the same configuration file as server nodes, so, you can define it there. Best Regards, Evgenii вт, 15 янв. 2019 г. в 09:33, garima.j : > Hello, > > While going through the documents, I read that to enable basic > authentication, i can enable th

Re: Ignite does not perform as expected

What do you mean? Only one index can be used for table for a one query. If you want to filter by 2 fields, you have to create group index. пн, 7 янв. 2019 г. в 17:38, Justin Ji : > Thank for your reply. > > How can I use devId as my index when only one index can be used for one > table > > > > --

Re: nodes getting disconnected from cluster

Hi, Can you share logs from all nodes, especially from node qagmscore02/ 10.114.113.53:47500 ? Evgenii пн, 7 янв. 2019 г. в 08:14, Akash Shinde : > Hi, > Someone could please help me on this issue. > > Thanks, > Akash > > On Thu, Jan 3, 2019 at 5:46 PM Akash Shinde wrote: > >> Hi, >> >> I am g

Re: Ignite does not perform as expected

Ignite can use only one index per table, so, you probably need to create a group index: https://apacheignite-sql.readme.io/docs/schema-and-indexes#section-group-indexes Evgenii пн, 7 янв. 2019 г. в 06:47, Justin Ji : > when I run a SQL query with the two indexes, but ignite does not perform as >

Re: Ouch! Argument is invalid: Cache name must not be null or empty.

As you see, the example in config has , which means that it's just a part of the configuration. Exceptions message says "Cache name must not be null" and that really the problem that you faced, just define cache name property to resolve this issue. Evgenii чт, 27 дек. 2018 г. в 22:28, yangjiajun

Re: Ignite Remote Node

Hi, By default, Ignite uses TcpDiscoveryMulticastIpFinder, which means that nodes can be connected to each other even without configuring certain IP addresses. You can use TcpDiscoveryVmIpFinder instead, it will try to connect only to the pre-configured addresses. TcpDiscoverySpi discovery = new

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

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

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

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. E

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: http://apache-ignite-users.70518.x6.nabble.c

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. I

Re: Ignite Query Slow

Hi, I'd say that it's normal to have bigger latency in the case when you starting more queries simultaneously than you have threads in query pool( https://apacheignite.readme.io/docs/thread-pools#section-queries-pool) and cores) Some of the queries will wait till other will finish. As for the thi

Re: Ignite startu is very slow

How about to create a new cache with the new partition count and move all the data from the previous one? After that repeat this process for each cache. Best Regards, Evgenii вт, 4 дек. 2018 г. в 21:14, kvenkatramtreddy : > Hi, > > Sorry to bother you. All Data in Ignite native persistence, so p

Re: Ignite startu is very slow

Hi, I'd say that 128 partitions should be more than enough for 3 nodes, just try it. Note: you will need to reload all data in caches, because they will have different affinity. Best Regards, Evgenii вт, 4 дек. 2018 г. в 02:36, kvenkatramtreddy : > Hi, > > Please could you suggest the number o

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 startu is very slow

Hi, You have a pretty small amount of heap and 30 caches. Each cache creates some overhead for node startup, because node should read states for each partition of each cache(and each partition is a separate file). You can reduce this overhead by configuring the same cache group: https://apacheigni

Re: Ignite startu is very slow

I've asked for the logs of node startup, not the log for stopping the cluster. Evgenii вт, 27 нояб. 2018 г. в 23:19, kvenkatramtreddy : > Hi, > Please find attached log. > ignite_deactivate.log > < > http://apache-ignite-users.70518.x6.nabble.com/file/t1700/ignite_deactivate.log> > > > whole clu

Re: Values lost when cache is in partitioned mode in cluster

Well, it's not a reproducer - it doesn't have any test or main classes, and, moreover, it has a lot of dependencies on classes, that were not provided. As for writeSynchronizationMode - with default PRIMARY_SYNC value, Ignite waits only till primary copy will be updated, so, you may need to wait s

Re: Ignite startu is very slow

Can you share logs from a startup after deactivation? Evgenii пн, 26 нояб. 2018 г. в 20:58, kvenkatramtreddy : > Hi, > > I have deActivated the cluster and closed, but still same issue persists. > > Thanks & Regards, > Venkat > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com

Re: Optimum storage startegy (Advice?)

Hi, You mentioned that all fields are indexed, does this mean that you have only single-field indexes? Do you consider creating group indexes for your queries? Can you share query plans with us? If you will have proper group indexes for all queries, maybe it worth to try to avoid joins at all and

Re: Values lost when cache is in partitioned mode in cluster

Hi, Do you flush data in data streamer? Can you share a simple reproducer? Best Regards, Evgenii пн, 26 нояб. 2018 г. в 11:18, the_palakkaran : > Hi, > > I have two nodes. A cache which has an Object as Key and a list of Objects > as values is configured in partitioned mode. On a single node ev

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: How to write Trigger Script

https://apacheignite.readme.io/docs/continuous-queries сб, 24 нояб. 2018 г. в 03:55, Malashreepolo : > How to write Triggers in Ignite Database. > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >

Re: BinaryObject nested fields syntax?

Hi, In this case, customer should be also a BinaryObject, so, you have to access it at first and only after get a certain field. Evgenii сб, 24 нояб. 2018 г. в 00:38, joseheitor : > Given the following model data structure for a given document record: > > { > "trans": { > "cust": { >

Re: Are QuerySqlField indexes used in ScanQueries?

Hi, No, ScanQuery doesn't use QuerySqlField indexes Evgenii сб, 24 нояб. 2018 г. в 01:34, joseheitor : > If model class fields are annotated with: > > @QuerySqlField(index = true) > > ... will ScanQueries with IgniteBiPredicates on the annotated fields > leverage the indexes? > > > > -- > Sent

Re: Ignite startu is very slow

For this particular case, it's just enough to stop cluster gracefully before starting it again. Just deactivate cluster before stopping. In this case, when you will start the nodes again, they won't need to apply WAL changes. Evgenii вс, 25 нояб. 2018 г. в 04:54, kvenkatramtreddy : > Heap size i

Re: Does a Ignite Cache return size metrics for a cache in local mode

Hi, Answered you on stackoverflow: https://stackoverflow.com/questions/53193997/does-a-ignite-cache-return-metrics-for-a-cache-in-local-mode/53453990#53453990 Evgenii пн, 19 нояб. 2018 г. в 12:39, Paddy : > I posted this on Stack Overflow a while back, but this is probably a better > place for

Re: Local messaging not happening asynchronously

Hi, It is an optimization, that runs operations which could be executed locally, in user thread. The same will work for cache operations too. First of all, do you really need to send a message to all nodes, including the local? You can send the message to the remote nodes only, it will automatica

Re: Does ignite keep loading result when the jdbc thin connection is dead?

Hi, What do you mean by "Ignite does not release memory"? What kind of memory it still consume? Do you mean heap? Evgenii чт, 22 нояб. 2018 г. в 15:55, yangjiajun <1371549...@qq.com>: > Hello. > > I use jdbc thin connection to access ignite with lazy mode.Ignite does not > release memory after

Re: LIKE operator issue in Ignite Database

Hi, Do you have a small reproducer for this? I've tried to create a simple one(see attached), but it works for me. Evgenii чт, 22 нояб. 2018 г. в 12:18, Shravya Nethula < shravya.neth...@aline-consulting.com>: > Hi, > > We are trying to execute the following select queries with LIKE operator: >

Re: Ignite startu is very slow

Hi, How many heap do you have? >From logs I see, that before this, cluster was not stopped properly and the checkpoint was not saved to the disk. Because of that, after the start, nodes started to applying WAL changes( https://apacheignite.readme.io/docs/write-ahead-log). It took 1491578ms, proba

Re: In which case will ignite run following sql?

Hi, Ignite doesn't run a query like this internally. It's executed in client-connector pool, which means that one of your JDBC or ODBC drivers send this query. How often do you see something like that? Evgenii чт, 22 нояб. 2018 г. в 15:13, yangjiajun <1371549...@qq.com>: > Hello. > > I found a

Re: Why drop table operations affect all update operations.

Hi, "DROP table" operation also destroying an underlying cache. This change should be properly synchronized between all the nodes, that's why it sends a special Discovery message to all nodes with the new minor topology change. Without this, not all nodes in the cluster will know about stopping th

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: New added property with @QuerySqlField does not persist

Hi, If you want to change sql schema after start, you have to use ALTER TABLE command: https://apacheignite-sql.readme.io/docs/alter-table Best Regards, Evgenii вт, 20 нояб. 2018 г. в 06:37, kcheng.mvp : > i noticed there is a comment from @slava.koptilin > > > I think the problem is to support

Re: Data not getting distributed across the cluster.

Hi, Why did you set rebalance delay to 12? Can you share model with us? Or, maybe, a simple reproducer? Do you have an affinityKey? Evgenii пт, 16 нояб. 2018 г. в 16:05, KR Kumar : > Hi - I have a application where the writes happens mostly from one node and > reads/compute happens on all t

Re: DataStreamer

Hi, Can you share the full code? Especially when you're closing it or flushing. Evgenii пт, 16 нояб. 2018 г. в 17:43, KR Kumar : > Following code creates the data streamer instance > > dataStreamer = > IgniteContextWrapper.getInstance().getEngine().dataStreamer("eventCache-" + >

Re: DataStreamer

Hi, Can you share the code when you load data with DataStreamer? Evgenii пт, 16 нояб. 2018 г. в 16:02, KR Kumar : > Hi Guys - I have a weird problem. when I am using data streamer to write > data > to ignite ( file based persistence), not all the entries are getting > persisted as later some ge

Re: SQL Support for IN predicate

Ray, By the way, which version do you use? Evgenii чт, 15 нояб. 2018 г. в 09:38, Evgenii Zhuravlev : > In any case, answer for replacing '?' with variables also placed on the > same page I've shared earlier. > > Evgenii > > чт, 15 нояб. 2018 г. в 08:25, Ray : &

Re: SQL Support for IN predicate

In any case, answer for replacing '?' with variables also placed on the same page I've shared earlier. Evgenii чт, 15 нояб. 2018 г. в 08:25, Ray : > Hello Evgenii, > > I have a question about IN clause not using indexes. > > From my local test results, it seems IN clause does use indexes. > > I

Re: SQL Support for IN predicate

Hi, IN clause is supported, however, it doesn't use indexes for now. It's better to replace it with a join to the temporary table: https://apacheignite-sql.readme.io/docs/performance-and-debugging#sql-performance-and-usability-considerations - paragraph 2. Evgenii ср, 14 нояб. 2018 г. в 23:26, R

Re: Can't add new key/value pair to existing cache via sql command

>then we can use `cache group` to share some backend data struct to gain some level performance. It will reduce the overhead for each cache since they will share the same data structures under the hood. >Are there any potential issues or potential consideration need to be takecare of? Caches in on

Re: Can't add new key/value pair to existing cache via sql command

cache and schema is a different things in Ignite. By default, when you create table with SQL, it will be created in separate cache. Evgenii пн, 12 нояб. 2018 г. в 20:00, kcheng.mvp : > based on my knowledge about ignite, there is a corresponding database > `schema` for each `cache` in ignite (c

Re: Can't add new key/value pair to existing cache via sql command

>can you tell me why there is a such limit that new created table via sql can not be in the non-public schema? It is a current restriction, that will be fixed in the future. >as it's hard to forecast how many tables should be in a caches. If there is a such limit, then what's the best practice whe

Re: JDBC thin: support connection pooling in 2.7?

Hi, This ticket is created for support of internal connection pooling, i.e. Ignite's implementation. As for now, you can use external connection pooling providers, like DBCP or c3p0. Please let us know if you will have any problems with that. Evgenii пт, 9 нояб. 2018 г. в 0:42, kcheng.mvp : > >

Re: Can't add new key/value pair to existing cache via sql command

Hi, If you want to use pre-defined cache, that already exists in the cluster for Creating new SQL Tables, it should have configured Public CacheConfiguration.sqlSchema: Evgenii пт, 9 нояб. 2018 г. в 12:53, kcheng.mvp : > my cache is created via (cache name is 'abc') > *igniteSpringBean.getOrC

Re: Ouch! Argument is invalid: Cache name must not be null or empty.

>1) How do I enable DEBUG logging on the Ignite cluster? It depends on the logger that you use. You have to change the config file and give to the ignite package DEBUG level. It could be JUL, log4j or log4j2 config files. > org.apache.ignite.spi.discovery.tcp.ClientImpl.joinTopology Client node di

Re: Sql long running queries

Hi, Can you run EXPLAIN for these queries so we can see the indexes that were used? Evgenii чт, 8 нояб. 2018 г. в 21:23, Ranjit Sahu : > Hi guys, > > I have the following query which is slow. Below is the explain plan. Any > clue whats going wrong ? > > > > [WARNING][client-connector-#62][Ignit

Re: java.lang.UnsupportedOperationException: Invalid fast index type: -21

Hi, I've added the same field to one of the objects in Ignite example and everything works fine. Can you share the full reproducer or at least the whole object? Thanks, Evgenii чт, 1 нояб. 2018 г. в 15:11, Yuriy : > I have made the index on bite[] field: > @QuerySqlField (index = true, notN

Re: Ouch! Argument is invalid: Cache name must not be null or empty.

IGNITE_QUIET=false enables only INFO logging. Well, then something stuck on the Zeppelin side, still it worth to collect the thread dumps from it. Evgenii пт, 2 нояб. 2018 г. в 10:39, sv : > Actually, I already am running each Ignite node with IGNITE_QUIET=false, so > that should already have IN

Re: Ouch! Argument is invalid: Cache name must not be null or empty.

> executing scala code (using %ignite) makes the entire Ignite interpreter in Zeppelin hang, without any errors in logs. How do I debug this? When something hangs, you have to check thread dumps to understand where and why it hangs. Also, sometimes, it worth to enable another level of the logging

Re: Ignite locking when affinity is used.

On the page, that I've shared earlier, you can find that locks will be acquired on primary and backup nodes. You see timeout=53696 because this is the remaining time after acquiring a lock on the previous node. Evgenii вт, 30 окт. 2018 г. в 8:18, kotamrajuyashasvi : > Hi > > Need help on the abo

Re: Configure Timeout for client in case server nodes are not up

Hi, connectionTimeout is related to different things. The timeout that you searching for is joinTimeout. By default it's unlimited. https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/spi/discovery/tcp/TcpDiscoverySpi.html#setJoinTimeout-long- Evgenii пн, 29 окт. 2018 г. в 14:18

Re: Ouch! Argument is invalid: Cache name must not be null or empty.

Hi, Looks like you use JDBC client driver, which needs cache name to be configured(https://apacheignite-sql.readme.io/docs/jdbc-client-driver). I'd recommend using a thin JDBC driver instead - it doesn't need.( https://apacheignite-sql.readme.io/docs/jdbc-driver) Evgenii пн, 29 окт. 2018 г. в 10

Re: Ignite locking when affinity is used.

Hi, Here is an Ignite Key-Value Transactions Architecture design duocment: https://cwiki.apache.org/confluence/display/IGNITE/Ignite+Key-Value+Transactions+Architecture#IgniteKey-ValueTransactionsArchitecture-Transactions Evgenii чт, 25 окт. 2018 г. в 9:56, kotamrajuyashasvi : > Hi > > In my ig

Re: Off heap limit

https://apacheignite.readme.io/docs/memory-configuration чт, 25 окт. 2018 г. в 7:25, Prasad Bhalerao : > Hi, > > Is there any limit for off heap memory? > > Thanks, > Prasad >

Re: Keycloak integration with Ignite

Hi, As far as I know, Ignite doesn't support all operations that needed for initial schema creation for Keycloak as now, because there is a lot of operations with table changing. However, you can try to rewrite these SQL scripts or create this schema in other DBs and then dump schema from 3rd part

Re: Query execution too long even after providing index

Well, looks like you trying to find the segments that intersects defined segment, but you're complicating it. You don't need 3 conditions here - it will be enough to have only one - ipStart <= MAX and ipEnd >= MIN. I've checked it for your case and got absolutely the same results as you have with a

Re: Ignite Service Grid - Anomalous behavior

Without it, you can't just understand, which data you should upload to each node. ср, 17 окт. 2018 г. в 12:03, Evgenii Zhuravlev : > Yes, in case if you use not partition-aware CacheStore > > Evgenii > > вт, 16 окт. 2018 г. в 22:36, the_palakkaran : > >> Does it me

Re: Ignite Service Grid - Anomalous behavior

Yes, in case if you use not partition-aware CacheStore Evgenii вт, 16 окт. 2018 г. в 22:36, the_palakkaran : > Does it mean all data will be loaded on all servers and then it will > partition amongst them ? > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >

<    1   2   3   4   5   6   >