RE: Re: Re: Re: Re: Re: Embedded mode - open source version + cluster configuration

It's because there is a big platform, which is considered for migration and ignite should be running in embedded mode to preserve similar architecture setup On 2025/10/02 17:00:07 Stephen Darlington wrote: > I'm curious: why embedded mode? Most people find the server mode simpler to > deploy an

Re: Re: Re: Re: Re: Embedded mode - open source version + cluster configuration

I'm curious: why embedded mode? Most people find the server mode simpler to deploy and use. On Thu, 2 Oct 2025 at 17:56, Ihor Parashynets wrote: > That was it - a duplicated port for the client connectors config (my bad > :facepaml). > > It works now as expected. Many thanks for your help! > > I

RE: Re: Re: Re: Re: Embedded mode - open source version + cluster configuration

That was it - a duplicated port for the client connectors config (my bad :facepaml). It works now as expected. Many thanks for your help! I can move now on with the PoC for our big migration... Best regards On 2025/10/02 15:47:20 Aleksandr Polovtsev wrote: > Could you please clarify, which

Re: Re: Re: Re: Embedded mode - open source version + cluster configuration

Could you please clarify, which exceptions you are experiencing? Your POC looks alright, the only issue is the `ignite.clientConnector.port` property, which is the same in all configs, they must be different if you are running the nodes on the same machine. Also please make sure to add the `--add-

RE: Re: Re: Re: Embedded mode - open source version + cluster configuration

Thanks for the hint - I got the point. Now I'm getting some weird behavior when starting the cluster that way - exceptions, some nodes go down, etc. May I ask you for additional verification on a dumb PoC, which I created as a maven project? I'm attaching it here - it has 3 dedicated classes, whi

Re: Re: Re: Embedded mode - open source version + cluster configuration

Thank you for the provided information, I was able to reproduce the issue. The problem is with the non-intuitive Embedded API, which is targeted at running single-node clusters. To solve your problem, you need to call `IgniteServer#waitForInitAsync` on other two nodes, for example: InitParameters

Re: Apache 2.X.X upgraded to 3.X.X

uration() class existed for that propose. > > > Best Regards | Com os melhores cumprimentos, > João Lola > -- > *De:* João Lola > *Enviado:* 21 de agosto de 2025 15:26 > *Para:* user@ignite.apache.org > *Assunto:* RE: Apache 2.X.X upgraded to 3.

Re: Re: Embedded mode - open source version + cluster configuration

Could you please attach the logs from the nodes you are running? The code looks correct to me. On Wed, Oct 1, 2025 at 7:54 PM Ihor Parashynets wrote: > Many thanks for the answer. > > Trying to switch from Hazelcast 5.x to the ignine 3, I'd like to ask > one additional question if I may - after

Re: Ignite 3.0 Features Roadmap

Thanks! Em sex., 12 de set. de 2025 às 00:58, Pavel Tupitsyn escreveu: > I think that might be coming in later releases. We certainly need > "rack/zone awareness" in Ignite 3. > > On Thu, Sep 11, 2025 at 4:44 PM Felipe Kersting > wrote: > > > > Hi Pavel, > > > > Thanks a lot for the response! >

Re: Ignite 3.0 Features Roadmap

I think that might be coming in later releases. We certainly need "rack/zone awareness" in Ignite 3. On Thu, Sep 11, 2025 at 4:44 PM Felipe Kersting wrote: > > Hi Pavel, > > Thanks a lot for the response! > > For (3), we checked distribution zones, but they do not look as flexible as > Ignite 2.

Re: Ignite 3.0 Features Roadmap

Hi Pavel, Thanks a lot for the response! For (3), we checked distribution zones, but they do not look as flexible as Ignite 2.17's backup filters. Ideally, we would like to have a big zone with a lot of nodes, thus allowing the data of a given table to be distributed across all available zones, b

Re: Apache 2.17 Security Vulnerability sonatype-2021-4292 sonatype-2022-5219

Hi, The memory leak described in sonatype-2021-4292 was fixed a long time ago, but could you provide more details about the affected versions and specific lines of code? пн, 25 авг. 2025 г. в 16:39, João Lola : > > Hello, > > I am currently analyzing my security reports for my Apache ignite 2.17

Re: BinarySerializer called for serialization of non-serializable Ignite class FastSizeDeque

Hi, Is it full stacktrace? Do you have full logs of your cluster and application? Could you attach your code and configuration? Best regards, Ilya Shishkov ср, 10 сент. 2025 г. в 21:43, Mathias Roeppischer : > > I experienced this issue with Ignite Core 2.17.0. The following error log was > wr

Re: Ignite 3.0 Features Roadmap

Hello Felipe, > Support for Near Caches in the client side Not on the road map as far as I know. > Support for "unstructured caches", i.e., caches that may be accessed as > simple put/get maps Already possible with KeyValueView [1]. You may need to provide a Mapper with custom TypeConverter

Re: Possible issue with class inheritance support in annotated POJO table creation

Hello. Unfortunately, the DSL catalog API does not support inheritance for several reasons. In your message, for some reason, you only look at the declaration of the parent class fields,but do not look that the parent itself can also have Table annotations or something else, which creates a lot of

Re: Ignite 3 and Availability Zones

Hi Sergey, Thank you for your answer. I believe not having an optimal communication pattern between the nodes is not a major problem. I was more concerned with the distribution of the backup replicas: it is important to ensure that the backups are always stored in nodes that belong to different A

Re: Ignite 3 and Availability Zones

Hello Felipe, At the moment Ignite 2.x isn't optimized for deployments spanning several Availability Zones so even if using the filter you mentioned with right configuration some operations may still suffer from increased delays between AZs. For instance, fulfilling a request from a remote AZ even

Re: Suggestion request - How can I go deeper in understanding Ignite?

t&uid=ddd_ot%40163.com&iconUrl=https%3A%2F%2Fmail-online.nosdn.127.net%2Fqiyelogo%2FdefaultAvatar.png&items=%5B%22ddd_ot%40163.com%22%5D> > Replied Message > From Maksim Timonin > Date 8/19/2025 16:21 > To > Subject Re: Suggestion request - How can I go dee

Re: Suggestion request - How can I go deeper in understanding Ignite?

to the deepwiki, it's a great AI bot and I've asked it tons of questions already. It's very helpful and convenient! Thank you for these valuable advice and websites you offered! They helped me a lot! Cup Aug 25, 2025 Replied Message | From | Maksim Timonin | | Date | 8/1

Re: Suggestion request - How can I go deeper in understanding Ignite?

s once again! Cup Aug 25, 2025 Replied Message | From | Sergey Chugunov | | Date | 8/19/2025 15:13 | | To | | | Subject | Re: Suggestion request - How can I go deeper in understanding Ignite? | Hello Cup, Apache Ignite source code is hard to grasp indeed and unfortunately there is no

RE: Apache Ignite 3.0.0 - Migration-tools-adapter

Lola De: Stephen Darlington Enviado: 21 de agosto de 2025 17:18 Para: user@ignite.apache.org Assunto: Re: Apache Ignite 3.0.0 - Migration-tools-adapter As Pavel said, it will be available in Ignite 3.1. What you're seeing there is the source code. If you want t

Re: Apache Ignite 3.0.0 - Migration-tools-adapter

As Pavel said, it will be available in Ignite 3.1. What you're seeing there is the source code. If you want to use it now, you'll need to build it yourself. On Thu, 21 Aug 2025 at 14:03, João Lola wrote: > Hello, > > I was investigating the migration-tools >

RE: Apache 2.X.X upgraded to 3.X.X

Thank you, Pavel. Best Regards | Com os melhores cumprimentos, João Lola De: Pavel Tupitsyn Enviado: 21 de agosto de 2025 15:07 Para: user@ignite.apache.org Assunto: Re: Apache 2.X.X upgraded to 3.X.X Migration tools are available at https://github.com/apache

Re: Apache 2.X.X upgraded to 3.X.X

de 2025 09:41 > Para: user@ignite.apache.org > Assunto: Re: Apache 2.X.X upgraded to 3.X.X > > Hi, > Do you have any sufficient reasons to migrate from 2.x.x right now? > > Apache Ignite 2.x.x is developed independently from 3.x.x and does not > become EOL for the foreseea

RE: Apache 2.X.X upgraded to 3.X.X

user@ignite.apache.org Assunto: Re: Apache 2.X.X upgraded to 3.X.X Hi, Do you have any sufficient reasons to migrate from 2.x.x right now? Apache Ignite 2.x.x is developed independently from 3.x.x and does not become EOL for the foreseeable future. вт, 6 мая 2025 г. в 18:32, João Lola : > > Hello

Re: Suggestion request - How can I go deeper in understanding Ignite?

Hello Cup, Recently I started to get down to read the source code Are you currently trying to solve a problem related to Apache Ignite? If so, the best approach is usually to *reproduce the issue*. Writing tests with the Ignite framework is a good starting point. For example, check these simple

Re: Suggestion request - How can I go deeper in understanding Ignite?

Hello Cup, Apache Ignite source code is hard to grasp indeed and unfortunately there is no detailed explanation for each and every class in its codebase. Some components of Ignite 2.x codebase are covered in wiki pages though: take a look at persistent store overview

Re: Ignite 3 Checkstyle improvement

Hello Ivan, This improvement would be a nice improvement to our code style. So, huge +1 from my side. Resending your mail to the dev list, because it is a contribution-related discussion. Tanks, S. вт, 5 авг. 2025 г. в 18:28, Ivan Zlenko : > Hi Ignite community! > I want to slightly improve ou

Re: Ignite 2.16 - entry missing in Continuous Query

Thanks for the suggestion, I added these checks. I was lucky this time, the tests ended up with the same error very quickly, in just 18 mins. Which, btw, tells how severe the problem is - with such chances to happen, it would definitely come up in PROD... Anyway - in the failed cycle all futures c

Re: Ignite 2.16 - entry missing in Continuous Query

Thanks Sergey, I will check it and will let you know (running the test cycle will take time). Notice however that the reader actually saw this key in its Ignite code, it has it in the logs. So I guess the entry came through, just was filtered out by Ignite as a "duplicate", as the log says. Also

Re: Ignite 2.16 - entry missing in Continuous Query

Hi, Does it still fail if wait all futures returned from the putAsync calls before exiting the writer app? Thanks, -- Sergey On 7/28/25 13:26, Michael Karmazin wrote: Hi, I’m contracting (via Algoteq I'm writing from here) for a Fortune 500 financial institution with a global footprint. I

Re: Ignite2.16 Cannot find class [io.prometheus.client.exporter.HTTPServer]

For reasons I don't quite understand, Ignite doesn't include the web server dependency. You need to add it yourself. I wrote a blog (with a GitHub repo) explaining how to do it: https://www.gridgain.com/resources/blog/integrating-prometheus-gridgain-or-apache-ignite On Wed, 23 Jul 2025 at 16:39,

Re: Query on AutoBaseLine Topology in .NET embedded service

do action and restart that node it will avoid below issue? Regards Satyajit Restricted - External *From:* Mandal, Satyajit: IT (PUN) *Sent:* Tuesday, July 15, 2025 10:09 PM *To:* user@ignite.apache.org *Subject:* RE: Query on AutoBaseLine Topology in .NET embedded service Hi Stephen

RE: Query on AutoBaseLine Topology in .NET embedded service

avoid below issue? Regards Satyajit Restricted - External From: Mandal, Satyajit: IT (PUN) Sent: Tuesday, July 15, 2025 10:09 PM To: user@ignite.apache.org<mailto:user@ignite.apache.org> Subject: RE: Query on AutoBaseLine Topology in .NET embedded service Hi Stephen, We are not ch

RE: Query on AutoBaseLine Topology in .NET embedded service

avoid below issue? Regards Satyajit Restricted - External From: Mandal, Satyajit: IT (PUN) Sent: Tuesday, July 15, 2025 10:09 PM To: user@ignite.apache.org Subject: RE: Query on AutoBaseLine Topology in .NET embedded service Hi Stephen, We are not changing the baseline topology. We observed

RE: Query on AutoBaseLine Topology in .NET embedded service

Satyajit Restricted - External From: Stephen Darlington Sent: Tuesday, July 15, 2025 8:08 PM To: user@ignite.apache.org Subject: Re: Query on AutoBaseLine Topology in .NET embedded service CAUTION: This email originated from outside our organization - user-return

Re: Query on AutoBaseLine Topology in .NET embedded service

icted - External > > -Original Message- > > From: Pavel Tupitsyn > > Sent: Tuesday, July 15, 2025 12:04 PM > > To: Mandal, Satyajit: IT (PUN) > > Cc: user@ignite.apache.org > > Subject: Re: Query on AutoBaseLine Topology in .NET embedded service > &g

RE: Query on AutoBaseLine Topology in .NET embedded service

/baseline-topology Regards Satyajit Restricted - External -Original Message- From: Pavel Tupitsyn Sent: Tuesday, July 15, 2025 1:33 PM To: Mandal, Satyajit: IT (PUN) Cc: user@ignite.apache.org Subject: Re: Query on AutoBaseLine Topology in .NET embedded service CAUTION: This email

Re: Query on AutoBaseLine Topology in .NET embedded service

es. So need to know what are the > options here to resolve this and get the baselinetopology updated? > > Regards > Satyajit > > > > > Restricted - External > -Original Message- > From: Pavel Tupitsyn > Sent: Tuesday, July 15, 2025 12:04 PM > To: Man

RE: Query on AutoBaseLine Topology in .NET embedded service

--Original Message- From: Pavel Tupitsyn Sent: Tuesday, July 15, 2025 12:04 PM To: Mandal, Satyajit: IT (PUN) Cc: user@ignite.apache.org Subject: Re: Query on AutoBaseLine Topology in .NET embedded service CAUTION: This email originated from outside our organization - user-return-36737-Satya

Re: Query on AutoBaseLine Topology in .NET embedded service

Hi Satyajit, not sure I understand the question. - Do you observe some unexpected behavior? - Does baseline auto adjustment work for you or not? On Tue, Jul 15, 2025 at 7:32 AM wrote: > > Hi Pavel, > > > > We are running ignite cache in embedded mode in .NET service with > persistence enabl

Re: Issue with IgnitionManager Class Missing in Ignite 3.0.0 for Embedded Mode

Unfortunately, it looks like the documentation is out of date. It should look something like this: Path myConfig = Path.of("conf/ignite-config.conf"); Path myWorkDir = Path.of("/home/ignite"); IgniteServer node = IgniteServer.start("node", myConfig, myWorkDir); InitParameters initParameters = In

Re: CVE 2024 52577: Ignite patched version Java 8 compatible

The community really only supports the current version. Of course, Ignite is open source so you could back-port the fix yourself. It looks like quite a large patch, so I'm not clear how easy it would be to backport and test. There are commercial options available if you search around. Regards, Ste

Re: Ignite 2.16 , Java 17 on server node and Java 8 on client node Error IgniteOutOfMemoryException: Out of memory in data region

Hi, Thanks for your email. Working fine once added data region configuration in c# client. Thanks Charlin On Thu, 19 Jun 2025 at 21:53, Stephen Darlington wrote: > Sorry, *here* is the documentation: > https://ignite.apache.org/docs/latest/net-specific/net-configuration-options > > > On Thu, 1

Re: Ignite 2.16 , Java 17 on server node and Java 8 on client node Error IgniteOutOfMemoryException: Out of memory in data region

Sorry, *here* is the documentation: https://ignite.apache.org/docs/latest/net-specific/net-configuration-options On Thu, 19 Jun 2025 at 15:37, Stephen Darlington wrote: > I don't know much about the .NET side of things, but I can say that it's > clearly not using your XML configuration file. Yo

Re: Ignite 2.16 , Java 17 on server node and Java 8 on client node Error IgniteOutOfMemoryException: Out of memory in data region

I don't know much about the .NET side of things, but I can say that it's clearly not using your XML configuration file. Your log is showing a different name, minimum and maximum data region size. Here's the documentation on configuring your servers from .NET. On Thu, 19 Jun 2025 at 14:24, Charli

Re: TLS warning "closing inbound before receiving peer's close_notify" during node startup

I ran across the same issue several months ago. I’m pretty certain it is harmless as no bugs have come up in our product since then. I didnt figure out a way to suppress the log or make it run “cleanly”. On Mon, May 19, 2025 at 07:01 Nandhini S wrote: > Hi Ignite Team, > > I'm currently using

Re: Use pattern to ensure queue messages are never lost

I suggest to implement your own queue logic with a transactional cache, here is an example to demonstrate the idea: https://gist.github.com/ptupitsyn/18a38db4dd1702558ebe273261f54233 On Sat, Jun 7, 2025 at 12:09 AM Alex Roytman wrote: > > Could anyone share your patterns for ensuring queue mes

Re: Can Queue be transactional

Thank you Pavel for the quick response so from the queue user perspective transactions are not applicable. Interestingly my quick test did not raise an exception simply added 2 items final IgniteQueue queue = ignite.queue("myQueue", 8, new CollectionConfiguration() .setAtomicityMode(CacheAtomi

Re: Inquiry: Fuzzy Search & Lucene Integration Support in Apache Ignite 3.x

Hi team, I would like to follow up on this question I had about Lucene integration in Ignite 3.0 To quickly recap: We’re working on a .NET-based application that requires fuzzy full-text search on in-memory data across millions of records. Ignite 2.x’s Lucene integration was a strong fit for thi

Re: Can Queue be transactional

Hello, With a transactional queue (CollectionConfiguration.atomicityMode = TRANSACTIONAL), the queue implementation starts a transaction internally [1]. If a transaction already exists in the current thread, queue operation will fail with "Failed to start new transaction (current thread already h

Re: Apache Ignite cache from MS SQL tables data,

You'd need to use some kind of CDC solution on the SQL Server side. On Mon, 12 May 2025 at 12:49, Charlin S wrote: > Hi All, > I am using Ignite 2.16 and looking for an option for creating an Ignite > cache same as MSSQL table. > Also data updates should happen whenever there are changes in MSSQ

Re: Apache 2.X.X upgraded to 3.X.X

gton > Enviado: 23 de abril de 2025 09:03 > Para: user@ignite.apache.org > Assunto: Re: Apache 2.X.X upgraded to 3.X.X > > The Spring Boot auoconfigurer exists: > https://mvnrepository.com/artifact/org.apache.ignite/spring-boot-ignite-client-autoconfigure > > On Tue,

RE: Apache 2.X.X upgraded to 3.X.X

: Stephen Darlington Enviado: 23 de abril de 2025 09:03 Para: user@ignite.apache.org Assunto: Re: Apache 2.X.X upgraded to 3.X.X The Spring Boot auoconfigurer exists: https://mvnrepository.com/artifact/org.apache.ignite/spring-boot-ignite-client-autoconfigure On Tue, 22 Apr 2025 at 23:02, Raj

Re: Apache 2.X.X upgraded to 3.X.X

>- import org.apache.ignite.events.EventType; >>>- import org.apache.ignite.lang.IgnitePredicate; >>> >>> >>> Best Regards | Com os melhores cumprimentos, >>> João Lola >>> -- >>> *De:* Stephen Dar

Re: Apache 2.X.X upgraded to 3.X.X

>>- import org.apache.ignite.lang.IgnitePredicate; >> >> >> Best Regards | Com os melhores cumprimentos, >> João Lola >> -- >> *De:* Stephen Darlington >> *Enviado:* 22 de abril de 2025 10:28 >> *Para:* user@ignite.ap

Re: Apache 2.X.X upgraded to 3.X.X

- > *De:* Stephen Darlington > *Enviado:* 22 de abril de 2025 10:28 > *Para:* user@ignite.apache.org > *Assunto:* Re: Apache 2.X.X upgraded to 3.X.X > > What do you mean by "full spring support"? What functionality are you > looking for? Ignite 3 no longer uses Sp

RE: Apache 2.X.X upgraded to 3.X.X

| Com os melhores cumprimentos, João Lola De: Stephen Darlington Enviado: 22 de abril de 2025 10:28 Para: user@ignite.apache.org Assunto: Re: Apache 2.X.X upgraded to 3.X.X What do you mean by "full spring support"? What functionality are you looking f

Re: Apache 2.X.X upgraded to 3.X.X

*Enviado:* 22 de abril de 2025 02:13 > *Para:* user@ignite.apache.org > *Assunto:* Re: Apache 2.X.X upgraded to 3.X.X > > I do see the annotations supported in Ignite 3 in addition to the > tabledescriptor builder API > > > https://ignite.apache.org/docs/ignite3/latest/developers-

RE: Apache 2.X.X upgraded to 3.X.X

De: Raj Enviado: 22 de abril de 2025 02:13 Para: user@ignite.apache.org Assunto: Re: Apache 2.X.X upgraded to 3.X.X I do see the annotations supported in Ignite 3 in addition to the tabledescriptor builder API https://ignite.apache.org/docs/ignite3/latest/developers-guide

Re: Apache 2.X.X upgraded to 3.X.X

I do see the annotations supported in Ignite 3 in addition to the tabledescriptor builder API https://ignite.apache.org/docs/ignite3/latest/developers-guide/java-to-tables Please check @Table, @Column and other annotations that are located in the org.apache.ignite.catalog.annotations package in

Re: Apache 2.X.X upgraded to 3.X.X

In Apache Ignite 3.0.0, the `@QuerySqlField` annotation has indeed been removed as part of a major architectural overhaul. This significant change affects how you define queryable fields in your domain models. For Ignite 3.0.0, the recommended approach is to use the new Table API instead of an

Re: Continuous query support in Ignite 3.0

Hello, - Continuous query is not yet supported in Ignite 3 - Might be added in later releases On Thu, Apr 10, 2025 at 2:30 AM Raj wrote: > > Hello, > Does ignite 3.0.0 Java client support continuous query API (connecting to > ignite 3 servers) similar to Ignite 2.x Java thin clients connecting

Re: Ignite log4j date not included

I'm afraid I'm not a log4j expert. You'd need to check their documentation: https://logging.apache.org/log4j/2.x/index.html On Fri, 4 Apr 2025 at 17:53, Charlin S wrote: > Hi Stephen, > Class not found error has been shortened by copy ignite-log4j2 folder from > optional to libs. RollingFile una

Re: Ignite 2.17 .NET error on startup.

em altogether and not > set it at all. > Happens on clean projects too. > Using versions up to 2.16 everything still works. > Current Java version: openJDK-17.0.9.9 (w JAVA_HOME set correctly) > > Any idea? > > Ethan > > > -Original Message- > From: satya

RE: Ignite 2.17 .NET error on startup.

Hi Pavel, Below error is resolved now. Regards Satyajit Restricted - External -Original Message- From: Pavel Tupitsyn Sent: Wednesday, April 2, 2025 12:30 PM To: user@ignite.apache.org Subject: Re: Ignite 2.17 .NET error on startup. CAUTION: This email originated from outside

RE: Ignite 2.17 .NET error on startup.

clean deployment in servers and it worked fine. Regards Satyajit Restricted - External -Original Message- From: Pavel Tupitsyn Sent: Wednesday, April 2, 2025 6:29 PM To: Mandal, Satyajit: IT (PUN) Cc: user@ignite.apache.org Subject: Re: Ignite 2.17 .NET error on startup

RE: Ignite 2.17 .NET error on startup.

... Thanks again and Best Regards, Ethan -Original Message- From: Pavel Tupitsyn Sent: Thursday, 3 April 2025 10:57 To: jay.et...@gmx.de Cc: user@ignite.apache.org; satyajit.man...@barclays.com Subject: Re: Ignite 2.17 .NET error on startup. Ethan, 1. Make sure IGNITE_HOME is not set

Re: Ignite 2.17 .NET error on startup.

-- > From: Pavel Tupitsyn > Sent: Wednesday, April 2, 2025 12:30 PM > To: user@ignite.apache.org > Subject: Re: Ignite 2.17 .NET error on startup. > > CAUTION: This email originated from outside our organization - > user-return-36677-Satyajit.Mandal=barclays@ignite.apac

Re: Ignite log4j date not included

Hi Stephen, Class not found error has been shortened by copy ignite-log4j2 folder from optional to libs. RollingFile unable to configure for this Thanks, Charlin On Thu, 3 Apr 2025 at 22:08, Charlin S wrote: > Hi Stephen, > Thanks for your email. > I am getting below error afte

Re: Ignite 2.17 .NET error on startup.

Looks like you have Java binaries from 2.16 and .NET binaries from 2.17. - Make sure that the IGNITE_HOME environment variable is not set, so that correct binaries are used from the NuGet package. - Do a clean build of your app - ensure that old binaries are not cached in bin/Debug or bin/Release

Re: Ignite log4j date not included

Hi Stephen, Thanks for your email. I am getting below error after adding gridlogger in springxml Exception has occurred: CLR/Apache.Ignite.Core.Common.IgniteException - Exception thrown: 'Apache.Ignite.Core.Common.IgniteException' in Apache.Ignite.Core.dll: 'Failed to instantiate configuration

Re: Ignite log4j date not included

Ignite doesn't use log4j by default, but it can be configured to do so: https://ignite.apache.org/docs/latest/logging#using-log4j2 The output format is also configurable. It's certainly possible to output errors to a different file from info and warnings. That configuration is not in Ignite but in

RE: Ignite 2.17 .NET error on startup.

openJDK-17.0.9.9 (w JAVA_HOME set correctly) Any idea? Ethan -Original Message- From: satyajit.mandal.barclays.com via user Sent: Thursday, 3 April 2025 05:17 To: user@ignite.apache.org; ptupit...@apache.org Subject: RE: Ignite 2.17 .NET error on startup. Hi Pavel, I removed the

RE: Ignite 2.17 .NET error on startup.

Same here. Cannot move to 2.17 because of it. Tested with: OpenJDK 11.0.18 OpenJDK 15.0.2 OpenJDK 17.0.9 All result in: JavaException: class org.apache.ignite.binary.BinaryObjectException: Unexpected field type Found no solution so far. Ethan From: satyajit.mandal.barclays.com vi

Re: sql in clause conversion from H2 to Calcite

Thanks. Really looking forward to it. ---Original--- From: "Alex Plehanov"

Re: sql in clause conversion from H2 to Calcite

Hello, Calcite engine in Ignite 2.16 can't expand the array parameter to table. It can be done with the UNNEST operator, but it's planned for 2.18 Ignite release. пн, 17 мар. 2025 г. в 15:49, MJ <6733...@qq.com>: > Ignite 2.16 > > Thanks, > MJ > > Original > -- > From

Re: sql in clause conversion from H2 to Calcite

Are you using Ignite 2 or Ignite 3? On Mon, 17 Mar 2025 at 11:15, MJ <6733...@qq.com> wrote: > Hi, > > Any idea how to convert H2's in clause sql to Calcite version ? For H2, > the sql - select * from tbl where col in (select col from (table col > varchar = ?)) works well with array objects as p

Re: sql in clause conversion from H2 to Calcite

Ignite 2.16 Thanks, MJ Original From:Stephen Darlington

Re: Queue Visibility Timeout

, but that reservation is revocable by a recovery feature. What's not clear is why a first attempt to process a queued item would fail and another attempt would succeed. In my experience it is better to catch the transaction rolling back and re-queue the failed item in a separate exception handlin

Re: Queue Visibility Timeout

Use case is for extended time processing of the messages which guarantee that a message is not lost from the queue if a client taking it fails to complete its processing and is not able to return it to the queue (ex crash, process termination, bug). It is how AWS defines its queue API https://docs.

Re: Queue Visibility Timeout

I don't think it's clear what you're trying to accomplish. Can you describe the desired behavior as a narrative? On Tue, Mar 4, 2025 at 5:42 PM Alex Roytman wrote: > Hello I was wondering if there is anything in Ignite queue to provide > behaviour similar to Queue Visibility Timeout or Processi

Re: Differentiating cache gets satisfied by in memory or persistent reads

I have raised Jira ticket https://issues.apache.org/jira/browse/IGNITE-24634 to capture this issue, and a related issue with cache local peeking reporting OffHeap presence after cold restart of grid. Raymond. On Tue, Feb 25, 2025 at 12:44 PM Raymond Wilson wrote: > Now I am confused. > > I have

Re: Differentiating cache gets satisfied by in memory or persistent reads

Now I am confused. I have configured caches correctly to enable statistics (both via configuration and via direct setting of the flag on an existing cache. When I log the results for cache statistics (number of Gets and number of off-help Gets), I notice two things: - The total number of off hea

Re: Differentiating cache gets satisfied by in memory or persistent reads

It seems you can modify cache statistics enablement for existing caches using the setter on the cache instance. I was setting this flag in the configuration for creating a new cache on the GetOrCreateCache(0 call, which of course is ignored if the cache already exists. I am still unsure why the pe

Re: Differentiating cache gets satisfied by in memory or persistent reads

FYI, I am using Ignite 2.16. I have also been playing with the Ignite metrics. This allows me to see the numbers of Get()'s for each cache, but I have a suspicion I can't enable it for existing caches.Is that correct? At least, when I enable it on an existing system I just get zeros back, but a ne

Re: SQL Query via REST API in Ignite 3.x

- Ignite 3 REST API spec is here: https://ignite.apache.org/releases/3.0.0/openapi.yaml - we'll add a link to the docs - SQL is not yet available via the REST API Please don't duplicate questions: https://stackoverflow.com/questions/79460381/qryexe-with-apache-v3-x-gridgain-9-x/79462713 On Sun,

Re: Differentiating cache gets satisfied by in memory or persistent reads

Apologies, Change { /* It was read from persistence */ } for { /* It needs to be read from persistence */ result = _cache.Get(key); } On Fri, Feb 21, 2025 at 12:39 PM Raymond Wilson wrote: > I am experimenting with some metrics to help us understand how often > Cache.Get() operations are sa

Re: Ignite 2.16 cache update taking longer time

You may have the opposite need compared to the problem expressed in this post: https://stackoverflow.com/questions/67598175/ignite-read-stale-data-from-backup-node If you want to serve up stale data from backup partitions while concurrent updates are happening on primary partitions, use backup pa

Re: [ANNOUNCE] Apache Ignite 3.0.0 Released

🎉 Huge milestone! Congratulations to all involved! On Mon, 10 Feb 2025 at 11:29, Pavel Tupitsyn wrote: > The Apache Ignite Community is pleased to announce the release of > Apache Ignite 3.0.0. > > Apache Ignite 3 is a distributed database for high-performance computing. > https://ignite.apach

Re: Ignite 2.16 thin client issue Failed to resolve class name

Please share the stack trace. Which API call is that? On Thu, Feb 6, 2025 at 2:57 PM Charlin S wrote: > Hi All, > I am trying to get cache data using thin client but throwing error Failed > to resolve class name [platformId=1, platform=.NET, typeId=***]. Same > working with tick clients. > Is th

Re: Updating ignite.

"The best way" (to use Ignite as a centralized cache) unfortunately leads to "it depends." There's many different styles of cache. https://www.geeksforgeeks.org/write-through-and-write-back-in-cache/ There's cache-aside, where you "memoize" your getters and setters so that getters try Ignite, and

Re: Updating ignite.

Yes, near cache. On Mon, Nov 18, 2024 at 3:01 PM Jeremy McMillan wrote: > When you say "local" cache, do you actually mean "near cache"? > https://ignite.apache.org/docs/latest/configuring-caches/near-cache > > If this is the case, I'd be interested to understand what would be lost > if, hypothe

Re: Ignite 2.16 KeyNotFoundException

Can you put together some shareable configuration/code/data that reproduces this issue in something like a GitHub gist and post that for the community to work on? That would be a good candidate for an Ignite GitHub issue ticket. On Mon, Feb 3, 2025 at 4:25 AM Charlin S wrote: > Hi All, > Thank y

Re: Affinity Keys in Ignite .NET for joining more than two caches

Hi, in this case you'll have to add the Employee.DepartmentId column and use department id as an affinity key in all caches. On Mon, Feb 3, 2025 at 9:13 AM wrote: > Hi Pavel, > > > > I have lets say three below caches and want to join using Affinity > key for these three caches so tha

Re: Ignite 2.16 KeyNotFoundException

Hi All, Thank you for your response. I am able to reproduce the same issue with *fullsync *mode. so I am suspecting this issue due to following steps under load. 1. Insert (success) 2. Read (success) 3. Update (success) 4. Read (Failed) Please suggest this to me. Tanks & Regards, Charlin On W

Re: Ignite 2.16 KeyNotFoundException

This code seems odd to me. It shouldn't matter if you're truly using FULL_SYNC, but this might invoke some corner case code path(s). First we set the cache mode to partitioned, then we make the number of backup partitions equal to running the cache in replicated mode. This makes me very suspicious

Re: Ignite 2.16 KeyNotFoundException

Hi All, TTL is defined at cache level and cache definition and configuration are CacheConfiguration cg = null; int nodeCount = IgniteInstanceDetail.IIgniteInstance.GetCluster(). ForServers().GetNodes().Count(); if (nodeCount == 0) { // If the node count is 0 then it will return from here i

Re: Ignite 2.16 KeyNotFoundException

Please also share your cache configuration. TTL is defined at the cache level. On Fri, 24 Jan 2025 at 06:55, Charlin S wrote: > Hi All, > I am trying for full_sync mode meanwhile I am having doubts on TTL. > TTL expires time is still longer. for me data not found happening in a > minute also. st

Re: Ignite 2.16 KeyNotFoundException

Hi All, I am trying for full_sync mode meanwhile I am having doubts on TTL. TTL expires time is still longer. for me data not found happening in a minute also. still I am not sure whether expiring data immediately or reading is happening from another node. My data region size 18GB and Java process

  1   2   3   4   5   6   7   8   9   10   >