Re: Concurrent merge into operations cause critical system error on ignite 2.7 node.

Hello. Please see the logs. ignite-8bdefd7a.zip ilya.kasnacheev wrote > Hello! > > Can you provide logs? > > Regards, > -- > Ilya Kasnacheev > > > вс, 13 янв. 2019 г. в 18:05, yangjiajun < > 1371549332@ >>

Is there a way to allow overwrite when set streaming on?

Hello. We can set streaming on while insert data to ignite using sql.I want to enable data overwrite in this mode.Is it possible? https://apacheignite-sql.readme.io/docs/set https://apacheignite.readme.io/docs/data-streamers#section-allow-overwrite -- Sent from: http://apache-ignite-users.7051

failure due to IGNITE_BPLUS_TREE_LOCK_RETRIES

On 2.7, we are regularly seeing the below message and then the nodes stop. [16:45:04,759][SEVERE][disco-event-worker-#63][] JVM will be halted immediately due to the failure: [failureCtx=FailureContext [type=CRITICAL_ERROR, err=class o.a.i.IgniteCheckedException: Maximum number of retries 1000 r

Baselined node rejoining crashes other baseline nodes - Duplicate Key Error

I have two nodes on which we have 3 tables which are partitioned. Index are also built on these tables. For 24 hours caches work fine. The tables are definitely distributed across both the nodes Node 2 reboots due to some issue - goes out of the baseline - comes back and joins the baseline. O

Re: Ignite 2.7 Client node security credentials configuration

I'm using IgniteConfiguration to provide the config while starting the node and not the XML file. I can't find a way to set the SecurityCredentials inside it. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

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: IgniteInterruptedException on cache.get in a transaction inside runnable (ignite 2.6)

The next time it happens, I will gather the logs. Thanks, Binti -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Ignite 2.7 Client node security credentials configuration

Hello, While going through the documents, I read that to enable basic authentication, i can enable the flag in XML. How do I provide the username/password when I connect to the cluster using a thick client node at another VM? I need to secure my cluster with a username/password so that no other

Re: Failed to wait for partition map exchange on cluster activation

Hello, You can find full log there: https://drive.google.com/file/d/1FwCjsXMw5LQJnKO0x5GNJ2w9gVsDbXlc/view?usp=sharing I can rerun tests with additional logging settings if needed Andrey. On Tue, Jan 15, 2019 at 6:23 PM Ilya Kasnacheev wrote: > Hello! > > Can you please upload the full v

Re: Visor "cache" command hangs when client node connects.

Yeah so far it works great inside DC/OS with marathon. On Tue, 15 Jan 2019 at 08:01, Ilya Kasnacheev wrote: > Hello! > > I think there were people on userlist who was able to open Dockerized > Ignite cluster to outside clients. I recommend searching archives. > > Regards, > -- > Ilya Kasnacheev

Re: Unable to activate an ignite cluster with multiple hosts.

Hi, as I can see you created a cluster without ignite native persistence, so it already active. Activation is required only when you created cluster with persistence: https://apacheignite.readme.io/docs/distributed-persistent-store Thanks, Mike. -- Sent from: http://apache-ignite-users.70518.

Re: Recovering from a data region OOM condition

What ignite version do you use? Could you please share a reproducer with us? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Failed to wait for partition map exchange on cluster activation

Hello! Can you please upload the full verbose log somewhere? Regards, -- Ilya Kasnacheev ср, 9 янв. 2019 г. в 20:43, Andrey Davydov : > > > Hello, > > I found in test logs of my project that Ignite warns about failed > partition maps exchange. In test environment 3 Ignite 2.7 server nodes run

Re: read from igniteRDD and write to igniteRDD

Hi Mehdi I think first you need to read the following doc: https://apacheignite-fs.readme.io/docs/ignitecontext-igniterdd it describes how to properly setup Ignite cluster and create IgniteRDD, also it has examples. if you still have a question after reading the documentation, please describe yo

Re: Ignite Visor cache command freezes, when client node connects.

Hello! Can you collect thread dumps during freeze? Regards, -- Ilya Kasnacheev пт, 11 янв. 2019 г. в 01:23, javadevmtl : > Hi, using 2.7.3 > > I start my client as... > > TcpDiscoverySpi spi = new TcpDiscoverySpi(); > TcpDiscoveryVmIpFinder ipFinder = new TcpDiscoveryVmIpFinde

Re: Again Failed to get page IO instance

Hello! It's hard to say judging from your stack trace alone. Why don't you try and see? Regards, -- Ilya Kasnacheev вт, 8 янв. 2019 г. в 01:24, wengyao04 : > Hi, we have ran ignite 2.6.0, and have 8 server in our base line > topology. > After we bounce the severs, our client starts writing u

Re: Not able to load data from Cassandra database to Ignite Cache.

Hello! > But here the requirement is first I need to load the data from cassandra database to ignite cache Have you tried loadCache()? Regards, -- Ilya Kasnacheev ср, 9 янв. 2019 г. в 16:08, Kiran Kumar : > Configured three xml files, one for cassandra connections, one for > persistence and

Re: SQLFieldsQuery timeout is not working

Looks like your query scans more then 4K rows to produce 200 rows result set. 15.01.2019 17:02, garima.j пишет: Hi, The number of rows in the table are 300k. In the SQL query, I specify the limit as 10. If I increase the limit to 200, it throws QueryCancelledException and times out. Is timeou

Re: SQLFieldsQuery timeout is not working

Hi, Timeout isn't dependent on the result set size but timeout is checked one time for 4K rows are scanned. 15.01.2019 17:02, garima.j пишет: Hi, The number of rows in the table are 300k. In the SQL query, I specify the limit as 10. If I increase the limit to 200, it throws QueryCancelledEx

Re: IgniteInterruptedException on cache.get in a transaction inside runnable (ignite 2.6)

Hello! I have no idea, maybe some kind of remote operation failed and caused domino effect. Do you have logs? Regards, -- Ilya Kasnacheev вт, 15 янв. 2019 г. в 17:17, bintisepaha : > Sorry, we are still on 2.3 :) > The timeout is 5 minutes on this transaction and it fails pretty quickly. > At

Re: IgniteInterruptedException on cache.get in a transaction inside runnable (ignite 2.6)

Sorry, we are still on 2.3 :) The timeout is 5 minutes on this transaction and it fails pretty quickly. At the same time, many threads fail at the exact same operation across nodes. Was there a similar bug in 2.3? We will be upgrading to 2.7 soon. -- Sent from: http://apache-ignite-users.70518

Re: SQLFieldsQuery timeout is not working

Hi, The number of rows in the table are 300k. In the SQL query, I specify the limit as 10. If I increase the limit to 200, it throws QueryCancelledException and times out. Is timeout dependent on the resultset size as well? Also, is there any way through which I can customize H2 timeout scanned

Re: Ignite Data Streamer Kafka version 2.0

Hi Mahesh, I do not think Kafka streamer uses any 2.x specific Kafka client APIs. From what you say I think kafka-client-1.1 (that Ignite 2.7 uses) cannot connect to Kafka 2.x cluster. Can you manually replace kafka-client-1.1.jar with kafka-client-2.0 jar on the Kafka streamer side and see if it

RE: SQLFieldsQuery timeout is not working

Hi, What’s your Ignite version? Can you share Ignite and cache configs and the query SQL? Thanks, Stan From: garima.j Sent: 15 января 2019 г. 14:18 To: user@ignite.apache.org Subject: SQLFieldsQuery timeout is not working Hello, I'm using the below code to execute a SQL fields query : SqlF

Re: SQLFieldsQuery timeout is not working

Hi, How many rows does the result set contains? How many rows are scanned to produce the result? Ignite use H2 as the SQL frontend. H2 checks the timeout after each 4K scanned rows. 15.01.2019 14:18, garima.j пишет: Hello, I'm using the below code to execute a SQL fields query : SqlFieldsQu

RE: Extra console output from logs.

Hi, First, try to disable IGNITE_QUIET. If still seeing duplicated messages after that, make sure you don’t have multiple slf4j adapters in the classpath. Let me know if that helps. Thanks, Stan From: javadevmtl Sent: 9 января 2019 г. 21:43 To: user@ignite.apache.org Subject: Re: Extra conso

Re: IgniteInterruptedException on cache.get in a transaction inside runnable (ignite 2.6)

Hello! You are saying you're on 2.6 but stack trace shows 2.3: ~[ignite-core-2.3.0.jar:2.3.0] Other than that, no reason why tasks submitted to a pool would NOT be interrupted by timeout if 'get' operation fails to finish timely. Need more context. Regards, -- Ilya Kasnacheev пн, 14 янв. 201

Re: NPE when start

Hello! Can you provide a small reproducer project? Regards, -- Ilya Kasnacheev сб, 12 янв. 2019 г. в 09:35, wangsan : > When a client node start with zk discovery and persistence enabled,Some > null > point exceptions will be throw (when the node start on a new machine ) > > The exception tra

Re: Concurrent merge into operations cause critical system error on ignite 2.7 node.

Hello! Can you provide logs? Regards, -- Ilya Kasnacheev вс, 13 янв. 2019 г. в 18:05, yangjiajun <1371549...@qq.com>: > Hello. > > I have a ignite 2.7 node with persistence enabled.I test concurrent merge > into operations on it and find below concurrent operations can cause > critical system

Re: Insert performance

Hello! This might be the point of IgniteDataStreamer (bigger latency, bigger throughput). However, you should be feeding data in parallel to IgniteDataStreamer, from multiple threads, for optimal performance. There are a lot of tuning considerations, such as thread pools, etc. Regards, -- Ilya

Re: MVCC and continuous query

Hello! Continuous Query is not event. We have three separate mechanisms with similar function: events, cache store, continuous query. It is possible that some supported and some aren't. Regards. -- Ilya Kasnacheev вт, 15 янв. 2019 г. в 03:28, Cindy Xing : > As per > https://apacheignite.read

RE: Thread got interrupted while trying to acquire table lock & Gotinterrupted while waiting for future to complete

Looks like the thread just ended. Do you see a similar issue? Do you have a reproducer? Stan From: bintisepaha Sent: 14 января 2019 г. 23:07 To: user@ignite.apache.org Subject: Re: Thread got interrupted while trying to acquire table lock & Gotinterrupted while waiting for future to complete

Re: Extra console output from logs.

Hello! As far as I can see Ignite is going to print its logo to stderr or stdout regardless of configured logger, along as some other output. Regards, -- Ilya Kasnacheev чт, 10 янв. 2019 г. в 21:25, javadevmtl : > Nobody has experienced this? I'm not trying to disable logs. I'm just > getting

Re: Visor "cache" command hangs when client node connects.

Hello! I think there were people on userlist who was able to open Dockerized Ignite cluster to outside clients. I recommend searching archives. Regards, -- Ilya Kasnacheev пн, 14 янв. 2019 г. в 21:54, John Smith : > So if it's all running inside DC/OS it works ni issues. So wondering what > w

Re: Ignite documentation error regarding RAM usage

Hi, The information on the page you referenced is correct. The default max size of the default data region is either 20% of RAM or 256MB, whichever is larger. The log message changed in https://issues.apache.org/jira/browse/IGNITE-7824 refers to something else. Perhaps, someone from the comm

SQLFieldsQuery timeout is not working

Hello, I'm using the below code to execute a SQL fields query : SqlFieldsQuery qry = new SqlFieldsQuery(jfsIgniteSQLFilter.getSQLQuery()).setTimeout(timeout,TimeUnit.MILLISECONDS); List listFromCache = cache.query(qry).getAll(); The query doesn't timeout at all. My timeout is 5 milliseconds

Re: Partitions stuck in MOVING state after upgrade to 2.7

I think I can comment this lines in org.apache.ignite.internal.processors.cache.distributed.dht.topology.GridDhtLocalPartition:     if (grp.walEnabled())     ctx.wal().log(new PartitionMetaStateRecord(grp.groupId(), id, state(), updateCounter())); PS. https://issues.apache.or