IgniteSpringBean & Ignite SpringTransactionManager broken with 2.4?

Hi, I see that with a change introduced in 2.4 in IgniteSpringBean to delay ignite instance start until all other spring beans are initialized may have broken Ignite SpringTransactionManager

Re: Ignite Spring Integration seems broken with 2.4 (upgrading from 2.3)

UPDATE : Moving to an @Bean method did not work aswell, getting below exception on startup. Looks like there is no way to configure SpringTransactionManager with IgniteSpringBean starting with 2.4...not sure how i can proceed with the upgrade..any idea anyone? lass]: Invocation of init method

Re: Ignite web console query

Hi Muthu, You can log the long-running queries by setting CacheConfiguration.queryDetailMetricsSize property to a maximum number of the queries to store. As for the transactions, starting Ignite 2.5, it will be possible to track running transactions started from an application. -- Denis On

Re: Ignite Spring Integration seems broken with 2.4 (upgrading from 2.3)

UPDATE : Below is the exception, ignite-object-manager - [ERROR] 2018-05-24 18:36:45.133 [main] org.springframework.boot.SpringApplication - Application startup failed org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'transactionManager' defined in class

Re: QueryEntity not reflecting ALTER TABLE changes made via DDL

Hello! Unfortunately there's no support in Native SQL API for table introspection. You could use thin client since it's fairly lighweight. Regards, -- Ilya Kasnacheev 2018-05-24 23:50 GMT+03:00 Nick Pordash : > Hi Illya, > > Is this possible to get without having to

Re: QueryEntity not reflecting ALTER TABLE changes made via DDL

Hi Illya, Is this possible to get without having to resort to JDBC? For example, the Ignite SQL Java Apis? -Nick On Mon, May 21, 2018, 5:56 AM Ilya Kasnacheev wrote: > Hello! > > Cache Configuration would only request its configuration at the time when > it was

Re: Client IgniteStreamer broken after cluster restart

Thanks, Ilya! On Tue, May 22, 2018, 10:15 AM Ilya Kasnacheev wrote: > Hello! > > What an awesome perdu monocle have you found! I have created a ticket > against Apache Ignite JIRA: > https://issues.apache.org/jira/browse/IGNITE-8564 > > Regards, > > -- > Ilya

Re: Ignite Spring Integration seems broken with 2.4 (upgrading from 2.3)

One thing i can do is to move the SpringTransactionManager bean instance creation into a @Bean method, i am going to test doing this once i get my machine back...but i wish i didn't have to change anything.. On Thu, May 24, 2018 at 12:54 PM, mlekshma wrote: > We are

Ignite Spring Integration seems broken with 2.4 (upgrading from 2.3)

We are upgrading from 2.3 to 2.4 & realized that a change made in IgniteSpringBean which is referenced in this added line in its javadoc resulted in us moving lots of references in PostConstruct to handleContextRefresh. "A note should be taken that Ignite instance is started after all other

Re: Ignite web console query

Hi Dennis, Is there a way to get & keep logging these long running queries & transactions? Thanks Muthu Regards, Muthu -- The real danger with modern technology isn't that machines will begin to think like people, but that people will begin to think like machines. -- Faith is to believe what

Ignite Spring Integration seems broken with 2.4 (upgrading from 2.3)

We are upgrading from 2.3 to 2.4 & realized that a change made in IgniteSpringBean which is referenced in this added line in its javadoc resulted in us moving lots of references in PostConstruct to handleContextRefresh. "A note should be taken that Ignite instance is started after all other

Re: C# client too slow to connect.

Hi Yakov, It works perfectly! Thanks!!! F.D. On Thu, May 24, 2018 at 11:17 AM Yakov Zhdanov wrote: > Hi, slow node join is possible on windows machines which is related to > tcp/ip stack differences from linux - windows implementation waits for the > entire timeout

Re: Re: Nodes can not join the cluster after reboot

Hi Evgenii, I am experiencing the same issue with grid affinity topology. We have a topology where we have 3 data nodes, 2 service nodes and several client nodes in the cluster. The issue occurs randomly sometimes when deploying the nodes. I wanted to know that the suggested solution of

Re: C# client too slow to connect.

Hi, slow node join is possible on windows machines which is related to tcp/ip stack differences from linux - windows implementation waits for the entire timeout which is 3000ms by defaull and linux returns immediately with "connection refuse". Just narrow the range - 10.200.20.90:47500..47509,

Re: Setting DefaultDataRegion to zero size

There is a validation for region size, so, you can't even create region with the less than 10 mb size. Off-heap can't be disabled at all, it's a core part of data grid architecture. Evgenii 2018-05-23 22:13 GMT+03:00 breischl : > Hi, > Thanks for the reply. We have enabled

Ignite benchmarking on K8s cluster

Hi, We are trying to use yardstick benchmark from gridgain (https://www.gridgain.com/resources/benchmarks/running-gridgain-benchmarks). These tests are mainly for a non K8s cluster. (based on the logic used in script). Is there any test suite which does benchmark test on K8s cluster. Regards,

Re: Binary type has different fields error

Deleted the second one. On Wed, May 23, 2018 at 11:06 PM, Raymond Wilson wrote: > Hi Pavel, > > > > Snap! I just created https://issues.apache.org/jira/browse/IGNITE-8590 > > > > Feel free to delete it. > > > > Thanks, > > Raymond > > > > *From:* Pavel Tupitsyn