Query timeout

Hi all, Is there any way to set query timeout parameter in JDBC url? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Query timeout

Hi, queryTimeout=N in seconds according with JDBC specification: java.sql.Statement#setQueryTimeout On 23.03.2020 12:47, breathem wrote: Hi all, Is there any way to set query timeout parameter in JDBC url? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/ -- Taras Ledkov Mai

Exporter usage of Ignite 2.8.0

Hi Team, Can you help how to use inbuilt exporter for Ignite 2.8.0. I read it in release notes that 'Added monitoring API - an exporter of Ignite metrics to external recipients'. Do we have to manually expose these exporters on some port ? Or are they exposed on any default port ? So that thes

Re: Query timeout

I try jdbc:ignite:thin://192.168.1.138:10800;queryTimeout=1 and jdbc:ignite:thin://192.168.1.138:10800?queryTimeout=1 both. Query is still executed more then 1 sec without exception. Is this parameter supported in 2.8.0? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: No ignitevisorcmd.sh in Ignite 2.8

Hi again I now downloaded the binary and started ignite in a screen. I started ignitevisorcmd.sh but can't connect to my running node with the 'open' command. I can connect to ignite with sqlline and inspect tables. Any clues? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Query timeout

Hi, Hm.. It works for me. Looks at the Ignite test: JdbcThinStatementTimeoutSelfTest#testQueryTimeoutRetrival [1]. Please share your simple reproducer or test. [1]. https://github.com/apache/ignite/blob/9f19e0160b1ca43a27908849ad46c65ebd8689f1/modules/clients/src/test/java/org/apache/ignite/

Re: Ignite memory leaks in 2.8.0

Hi, Thanks for your investigation. Root cause is clear. What use-case is causing the leak? I've created the issue to remove mess ThreadLocal logic from ConnectionManager. [1] We 've done it in GG Community Edition and it works OK. [1]. https://issues.apache.org/jira/browse/IGNITE-12804 On 21

Re: HOW TO CHANGE IGNITE JAVA THIN CLIENT PASSWORD

Hello! I have just rechecked this case: 1) start persistent node. 2) try changing password - failure (cluster not active) 3) activate cluster (control.sh --activate, ignite/ignite) 4) try changing password - success. 5) check with sqlline - new password (test) accepted. 6) try connecting with thin

Near cache configuration for partitioned cache

Hi, I am using Ignite 2.7.6 and I have 2 server nodes with one partitioned cache and configuration: http://www.springframework.org/schema/beans"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation=" http://www.springframework.org/schema/beans htt

Re: No ignitevisorcmd.sh in Ignite 2.8

Are you getting any error messages? Are you giving it the same configuration file as you give the server nodes? It works when I try it with the default options. > On 23 Mar 2020, at 12:03, joaogoncalves wrote: > > Hi again > > I now downloaded the binary and started ignite in a screen. > > I

Re: No ignitevisorcmd.sh in Ignite 2.8

I am starting ignite with my custom config file like: ./bin/ignite.sh config.xml Below is my config file: http://www.springframework.org/schema/beans"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation=" http://www.springframework.org/schema/beans http:/

Re: Data Isolation during Ignite Cache load

Hi , But it is not behaving that way. I have tested it using the following scenario. Scenario: Initially loading 1000 rows from oracle table with the following filter where rownum<=1000 into ignite cache. During the cache load process, i checked the count using sql fields query i got the respo

Re: No ignitevisorcmd.sh in Ignite 2.8

Are you starting ignitevisor on the same machine as your server? There’s no problem with your discovery configuration. I can use your configuration to start a server node and Visor on my laptop. > On 23 Mar 2020, at 15:38, joaogoncalves wrote: > > I am starting ignite with my custom config fil

Re: Ignite 2.8.0. Heap mem issue

Hi, I tried to reproduce the same problem using the provided information, but without success. In the log I see that there are operations running on the cluster that were not described in pseudo code, for example, SQL queries withh count. Are you running something else? Can you provide full reprod

Ignite.cache.loadcache.Does this method do Increamental Load?

Hi I am trying to load the data into ignite cache using JDBC Pojo Store method ignite.cache("cacheName").loadCache(null).I have used this method and got the following results for the following scenarios. *Scenario-1:Trying to load the same key which is available in cache* In this case, the valu

RE: Re: Ignite 2.8.0. Heap mem issue

As I see in heapDump: There are 29000+ connections stored here: this - value: org.apache.ignite.internal.processors.query.h2.H2ConnectionWrapper #1 <- key - class: java.util.concurrent.ConcurrentHashMap$Node, value: org.apache.ignite.internal.processors.query.h2.H2ConnectionWrapper #1  <- [

Re: Data Isolation during Ignite Cache load

Hi, > ignite should display the data prior to data load instead of displaying the data that isloaded till that point *What do you mean? How it will help with a problem that you describing after that? * > he might get an empty response in case if the requested data is notyet loaded when the cache l

Loading Data from RDMS to ignite using Data Streamer

Hi , I am new to Ignite. i am able to load data from oracle into ignite using Cache Pojo Store method ignite.cache.("cachename").loadcache(null) . But in the documentation it was mentioned that Data Steamers will provide better performance when loading data into ignite cache. *Documentation Refe

Re: No ignitevisorcmd.sh in Ignite 2.8

Yes, im running ignitevisor on the same machine. I've been testing, trying to start ignite with example config files, and I'm not able to connect to ignite with any of them. It starts up correctly, but I can't connect. I get no errors, except on one of them: Caused by: class org.apache.ignite.I

RE: Re: Ignite 2.8.0. Heap mem issue

Hi, in attachment is code for heap mem issue simulation. Ignite_2.zip # create cache TEST and insert random data into cache TEST test_insert_in_cache.py # read data from cache TEST and inset/update data in table TEST_TABL

Re: Ignite memory leaks in 2.8.0

It seems detached connection NEVER become attached to thread other it was born. Because borrow method always return object related to caller thread. I.e. all detached connection borned in joined thread are not collectable forewer. So possible reproduce scenario: start separate thread. Run in this

RE: Re: Ignite memory leaks in 2.8.0

Sorry, It was to http://apache-ignite-users.70518.x6.nabble.com/Ignite-2-8-0-Heap-mem-issue-td31755.html thread Andrey. От: Andrey DavydovОтправлено: 23 марта 2020 г. в 23:00Кому: user@ignite.apache.orgТема: Re: Ignite memory leaks in 2.8.0 It seems detached connection NEVER become attached to thre

RE: RE: Re: Ignite 2.8.0. Heap mem issue

It seems detached connection NEVER become attached to thread other it was born. Because borrow method always return object related to caller thread. I.e. all detached connection borned in joined thread are not collectable forewer. So possible reproduce scenario: start separate thread. Run in this t

Re: Python - Ignite 2.8.0 - java.lang.NullPointerException

Hi, I'm running this reproducer and I don't see any issues. Do you use pyignite from the same version? Can you please share the full log file, maybe we're missing something? Thanks, Evgenii пт, 20 мар. 2020 г. в 08:11, dbutkovic : > I have one small error in py code, please remove last "," from

Re: Ignite python module pygridgain - Connected to

Hi, In pyignite, Client extends Connection class, which has __repr__ implementation, while in pygridgain Client doesn't extends Connection class. In both cases Client doesn't have it's own representation. Evgenii сб, 21 мар. 2020 г. в 08:47, Dren Butković : > Hi, > I tested two Python Thin clie

Re: Near cache configuration for partitioned cache

Hi, Near Cache configuration in xml creates near caches for all nodes, including server nodes. As far as I understand, you want to have them on client side only, right? If so, I'd recommend to create them dynamically: https://www.gridgain.com/docs/latest/developers-guide/near-cache#creating-near-c