RE: Connecting External Client to Containerized Cluster in Kubernetes

We currently have working installation where our Ignite Server Nodes reside on the standalone VMs and form a Cluster upon start by using shared Configuration setup. Our Client application joins Cluster on-demand, loads data into the Cluster and then kicks-off certain operations on the loaded data.

RE: Data from multiple MySQL DBs

Hi Ilya, Thanks for your suggestion. So what you are suggesting is: * Run a Ignite single cluster which has the correct schemas * Develop a tool which regularly pulls data from all these MySQL DBs and that uses the Ignite Data Streamer API to update the Caches in the cluster *

RE: Connecting External Client to Containerized Cluster in Kubernetes

Hello Vitaly, Unfortunately, I am not aware of any working solution right now and it looks that the ticket related to special discovery mechanism for external cluster members is not in work currently: https://issues.apache.org/jira/browse/IGNITE-4161 You might find this mailing thread useful

Re: Perfomance drop

Hello! How we can debug it to find cache name that causes it? Some extra logging or metrics? Скачайте Outlook для Android From: Ilya Kasnacheev Sent: Wednesday, September 11, 2019 4:08:18 PM To: user@ignite.apache.org Subject: Re:

Re: Ignite Map-Reduce Deadlocking, Running in SYS pool

I respectfully suggest you update your public documentation ASAP, as people (like my team) are developing new software now, using IGFS, expecting that it will continue to be supported. Please don't wait until you release 2.8. On Wed, Sep 11, 2019 at 11:07 AM Ilya Kasnacheev wrote: > Hello! > >

Re: Users named "ignite" cannot change their password?

Hi, In addition to Ilia answer, please read next page: https://apacheignite-sql.readme.io/docs/create-user#section-description BR, Andrei 9/4/2019 11:47 AM, Ilya Kasnacheev пишет: Hello! User names are case sensitive and bound by SQL rules, i.e.: ALTER USER "ignite" WITH PASSWORD

Re: Grid failure on frequent cache creation/destroying

Thanks Ilya! Good to have confirmation. From: ilya.kasnach...@gmail.com At: 09/11/19 11:57:16To: Abhishek Gupta (BLOOMBERG/ 731 LEX ) Cc: user@ignite.apache.org Subject: Re: Grid failure on frequent cache creation/destroying Hello! I'm afraid that's

Re: Grid failure on frequent cache creation/destroying

Hello! I'm afraid that's https://issues.apache.org/jira/browse/IGNITE-12013 There's a maillist thread attached. Regards, -- Ilya Kasnacheev вт, 10 сент. 2019 г. в 00:33, Abhishek Gupta (BLOOMBERG/ 731 LEX) < agupta...@bloomberg.net>: > Hello, > We have a grid of 6 nodes with a main cache.

Re: Data region LRU offheap algo not working

Hi, it's in the log 2.7.5...Thanks for any help here! Thanks, Rick -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Data region LRU offheap algo not working

what is tour ignite version? - Russian telegram Ignite chat at https://t.me/RU_Ignite -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: IgniteCache.invoke deadlock example

Hello! Yes! You should always lock keys in the same order (they are usually sorted for that matter). Regards, -- Ilya Kasnacheev вт, 10 сент. 2019 г. в 22:39, Evangelos Morakis : > Hi Andrei, > Thanks a lot for your reply. Relatively to the dummy code I provided I > take it you mean the

Re: Data from multiple MySQL DBs

Hello! I think the best course will be to read all DBs in user code and use data streamer to populate Ignite. Regards, -- Ilya Kasnacheev вт, 10 сент. 2019 г. в 18:01, Kurt Semba : > Hi all, > > > > I need to sync data from multiple MySQL databases into Ignite. > > > > All those MySQL

Re: Ignite Map-Reduce Deadlocking, Running in SYS pool

Hello! https://issues.apache.org/jira/browse/IGNITE-11942 Vote already succeeded, there shouldn't be IGFS in 2.8. Regards, -- Ilya Kasnacheev ср, 11 сент. 2019 г. в 16:52, Chris Software : > Ilya, > > When will an official announcement and support-drop schedule be made about > dropping

Re: Iterator for keys only ?

Hello! You can also use ScanQuery with Transformer. Note that all key-value pairs will still be deserialized. If your key fits in index, it would indeed be better to use SQL. Regards, -- Ilya Kasnacheev ср, 11 сент. 2019 г. в 15:47, Mikael : > Hi! > > What is the best way to iterate over the

Re: write-behind cache performance bottleneck

Hello! Unfortunately we would need more information to answer either question. What's `normal write of the cache block`? Can you show some code? Regards, -- Ilya Kasnacheev пн, 9 сент. 2019 г. в 05:42, liyuj <18624049...@163.com>: > If only put operations, with very few updates, would

Re: NearCaches

Hello! Near cache only holds a subset of data from cache, so it's just a single cache any way. You can use CachePeekMode.NEAR to check if entries are cached near. Regards, -- Ilya Kasnacheev вс, 8 сент. 2019 г. в 21:47, Кузин Никита (Nikita Kuzin) < nku...@iitdgroup.ru>: > Hello! > > I

Re: How to execute an sql on a specific remote server?

Hello! You can set `local=true` to execute completely local requests, and you can connect your JDBC to NX with this option. Regards, -- Ilya Kasnacheev вс, 8 сент. 2019 г. в 20:44, livelace : > Hi, Andrew. I found this topic in Google. > > I have a case where: > > 1. I have two nodes (all

Re: Ignite Map-Reduce Deadlocking, Running in SYS pool

Ilya, When will an official announcement and support-drop schedule be made about dropping IGFS? Thank you, Chris On Tue, Aug 27, 2019 at 1:47 PM Chris Software wrote: > I see. Thank you. > > On Tue, Aug 27, 2019 at 12:30 PM Ilya Kasnacheev < > ilya.kasnach...@gmail.com> wrote: > >> Hello!

Re: Perfomance drop

Hello! I can see that there's huge unevenness with regards to striped pool usage: around 80% of load end up on just two striped threads, sys-stripe-11-#12%ITLXCLKAP-server425b5ae8-214a-4ff8-b1a4-943a1513c415% and sys-stripe-9-#10%ITLXCLKAP-server425b5ae8-214a-4ff8-b1a4-943a1513c415%. That's 2/3

RE: Iterator for keys only ?

Hello! You can try to use SqlFieldsQuery with “select _key from [CacheTable]” for that. From: Mikael Sent: Wednesday, September 11, 2019 3:47 PM To: user@ignite.apache.org Subject: Iterator for keys only ? Hi! What is the best way to iterate over the keys only from a cache ? I don't want the

Iterator for keys only ?

Hi! What is the best way to iterate over the keys only from a cache ? I don't want the values because these are long text strings so will slow down the iterator a lot. Pretty much the Ignite way of doing map.keySet().iterator(); Mikael

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

Hello, There is an open ticket https://issues.apache.org/jira/browse/IGNITE-12032 with more details. In general, It’s ok to ignore this error. You could try to follow Lev’s recommendations with explicit connection closing. From: Matan Levy Sent: Thursday, August 1, 2019 9:33 AM To:

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

Hi, @matanlevy This exception shows that your database connection wasn't correctly closed. It probably should be fixed by executing `connection.close()` method before process using thin clients finished. Could you please try this and tell the result? -- Sent from:

Complex Event Processing Using Ignite Streaming

I am trying to build a CEP where a Complex event needs to be generated on a set of input events (3 Chassis hot events) over a specified time window (10 seconds, for eg) and I am trying to evaluate Apache Ignite for this. Are there any examples of how to do Complex Event Processing using Ignite? 

Re: Ignition Start - Timeout if connection is unsuccessful

Mahesh, There is a TcpDiscoverySpi property, that defines this behaviour: TcpDiscoverySpi#joinTimeout [1]. So, instead of calling Ignition.start() with a special property, you can specify this timeout in the configuration. If a join attempt is failed and joinTimeout is already exceeded, then the

Ignition Start - Timeout if connection is unsuccessful

Hello We are currently using Ignition.Start to get the handle for thick client. >> ignite = Ignition.start(cfg); As I understand, this API is a blocking API, unless the connection is successfully established. However, in some scenarios, where the thick client is unable to connect properly,