Re: Micronaut/Ignite

The main reason why I was using the spring bean definition was mainly for convenience and I'm not sure what fields are the most relevant. Will have to be kind of specific since the configuration might get a little complicated. The other thing you can do is use https://docs.micronaut.io/latest/api/i

[jira] [Created] (IGNITE-13373) WAL segmentns do not released on releaseHistoryForPreloading()

Alexander Lapin created IGNITE-13373: Summary: WAL segmentns do not released on releaseHistoryForPreloading() Key: IGNITE-13373 URL: https://issues.apache.org/jira/browse/IGNITE-13373 Project: Ign

Re: Update of the default inline size for variable types

>Hi guys,   Evgeniy, hola! > >Currently if a varlength type (such as String or byte[]) is encountered in >the composite index inline size just defaults to 10, which is almost always >not enough. I am going to change this and implement following changes: > >1) For a column of the variable length k

Update of the default inline size for variable types

Hi guys, Currently if a varlength type (such as String or byte[]) is encountered in the composite index inline size just defaults to 10, which is almost always not enough. I am going to change this and implement following changes: 1) For a column of the variable length keep using 10 as the defaul

Re: Micronaut/Ignite

Its whatever is setup by default when the object is declared. I think we will have to define multiple ConfigurationBuilders If i'm not mistaken for the IgniteConfiguration. you don't need to provide the name since that is provided by the key for each configuration under EachProperty. The name is t

Re: Micronaut/Ignite

> > oh, so we probably don't need to work with multiple instances. This is what > I have in the current master branch. In most cases, people start a single instance of a thick or thin client per application. The clients are multi-threaded and can utilize all the CPUs effectively. However, it's no

Re: Stuck in solving class not found exception

Hi Belal, The following class wasn't found in the classpath of the node that failed with the exception Caused by: java.lang.ClassNotFoundException: com.globant.ignite.config.CutomStoreSessionListener at java.net.URLClassLoader.findClass(URLClassLoader.java:381) at java.lang.ClassL

Stuck in solving class not found exception

Hi Team, I am getting an exception when my client tries to connect to the cluster, i have copied my application jar in the libs folder of the cluster still did not get why this issue is coming, please help me ! I have written my application code in the spring boot gradle project which will act as

Re: Micronaut/Ignite

oh, so we probably don't need to work with multiple instances. This is what I have in the current master branch. I believe I was originally trying to set-up the configuration with the default ignite instance but found I couldn't cover enough of the configuration. So what defaults are set for Ignite

Re: BEAM-9045 Implement an Ignite runner using Apache Ignite compute grid

Hi Val, Thank you for your response. I like the idea of reactive event based processing engine for fault tolerance. As you mentioned it will be upto underlying system to manage job execution and offer fault tolerance and we will need to build it in Ignite compute execution model. I looked into Fl

Re: BEAM-9045 Implement an Ignite runner using Apache Ignite compute grid

Hi Saikat, Thanks for clarifying. Is there a Beam component that monitors the state, or this is up to the application? If something fails, will the application have to retry the whole pipeline? My concern is that Ignite compute actually provides very limited guarantees, especially for the async e

Re: Micronaut/Ignite

Michael, thanks for filling out the wiki page. I'm looking at the Auto-Configuration wiki section and the current version of the io.micronaut.ignite.configuration.IgniteClientConfiguration

Re: Apache Ignite 2.9.0 RELEASE [Time, Scope, Manager]

Ok, I'm just asking, there is no rush for this ticket. If the release is postponed anyway, I thought that we can include more fixes. On Tue, Aug 18, 2020 at 8:10 PM Alex Plehanov wrote: > Pavel, > > We still can't find the root cause of performance drop. > > Ticket IGNITE-13369 still in progress

Re: Operation block on Cluster recovery/rebalance.

John, thanks for filing. Back up the Ilya's proposal. I've changed the ticket from the improvement to the bug. - Denis On Tue, Aug 18, 2020 at 10:06 AM Ilya Kasnacheev wrote: > Hello! > > My opinion is that it should be filed as a bug and then fixed. > > Regards, > -- > Ilya Kasnacheev > > > с

Re: Apache Ignite 2.9.0 RELEASE [Time, Scope, Manager]

Pavel, We still can't find the root cause of performance drop. Ticket IGNITE-13369 still in progress. When it will be resolved? Is it really critical bug? According to the user-list thread attached to the ticket, there is a workaround exists for this problem and looks like it's not so critical.

Re: Operations block when cache is not active.

For everyone's reference: https://issues.apache.org/jira/browse/IGNITE-13372 On Tue, 18 Aug 2020 at 07:15, Ilya Kasnacheev wrote: > Hello! > > Please file an issue against Apache Ignite JIRA. > > https://issues.apache.org/jira/projects/IGNITE/issues > > Regards, > -- > Ilya Kasnacheev > > > сб,

[jira] [Created] (IGNITE-13372) Operations block when cluster becomes inactive.

None none created IGNITE-13372: -- Summary: Operations block when cluster becomes inactive. Key: IGNITE-13372 URL: https://issues.apache.org/jira/browse/IGNITE-13372 Project: Ignite Issue Type: Im

[jira] [Created] (IGNITE-13371) Sporadic partition inconsistency after historical rebalancing of updates with same key put-remove pattern

Ivan Rakov created IGNITE-13371: --- Summary: Sporadic partition inconsistency after historical rebalancing of updates with same key put-remove pattern Key: IGNITE-13371 URL: https://issues.apache.org/jira/browse/IGNIT

Re: Operations block when cache is not active.

Hello! Please file an issue against Apache Ignite JIRA. https://issues.apache.org/jira/projects/IGNITE/issues Regards, -- Ilya Kasnacheev сб, 15 авг. 2020 г. в 18:07, John Smith : > Hi I was told by Dennis to post this here. But basically he said to propose > a change not to make operations

Re: Apache Ignite 3.0

Hello! Maybe we can implement messaging via compute? Share underlying code but have a different API for convenience (maybe in extras). Regards, -- Ilya Kasnacheev вт, 18 авг. 2020 г. в 11:59, Pavel Tupitsyn : > Val, > > > Is see the ".NET Modernization for Ignite 3.0" item in the roadmap, but

[jira] [Created] (IGNITE-13370) Missed README.txt in ignite-control-utility module

Kirill Tkalenko created IGNITE-13370: Summary: Missed README.txt in ignite-control-utility module Key: IGNITE-13370 URL: https://issues.apache.org/jira/browse/IGNITE-13370 Project: Ignite

Re: Apache Ignite 2.9.0 RELEASE [Time, Scope, Manager]

Alex, What's the status of the release? Can we include a bug fix there [1]? [1] https://issues.apache.org/jira/browse/IGNITE-13369 On Fri, Aug 14, 2020 at 11:14 AM Alex Plehanov wrote: > Hello, > > > What is the release date for 2.9, from the cwiki it still says August 7 > We have a performanc

[jira] [Created] (IGNITE-13369) .NET: Local node info is not updated on client reconnect

Pavel Tupitsyn created IGNITE-13369: --- Summary: .NET: Local node info is not updated on client reconnect Key: IGNITE-13369 URL: https://issues.apache.org/jira/browse/IGNITE-13369 Project: Ignite

Re: Apache Ignite 3.0

Val, > Is see the ".NET Modernization for Ignite 3.0" item in the roadmap, but it > doesn't provide much detail. What are the actual changes in .NET that you > propose for 3.0? I've updated the roadmap with a brief description. We want to move away from an old, long unsupported .NET version, and

Re: [MTCGA]: new failures in builds [5539465] needs to be handled

Hi, It's my fail. I will fix it. https://issues.apache.org/jira/browse/IGNITE-13368 --  Best regards, Anton Kalashnikov 17.08.2020, 22:52, "dpavlov.ta...@gmail.com" : > Hi Igniters, > >  I've detected some new issue on TeamCity to be handled. You are more than > welcomed to help. > >  If your

[jira] [Created] (IGNITE-13368) Speed base throttling unexpectedly degraded to zero

Anton Kalashnikov created IGNITE-13368: -- Summary: Speed base throttling unexpectedly degraded to zero Key: IGNITE-13368 URL: https://issues.apache.org/jira/browse/IGNITE-13368 Project: Ignite

[jira] [Created] (IGNITE-13367) meta --remove command usage improvements

Sergey Chugunov created IGNITE-13367: Summary: meta --remove command usage improvements Key: IGNITE-13367 URL: https://issues.apache.org/jira/browse/IGNITE-13367 Project: Ignite Issue Typ