There is an example of and gentle introduction to building Ignite out of
Maven dependencies in the Ignite Essentials workshop. You could enroll in
an upcoming free training session or access the same material on your own
schedule for free on university.gridgain.com. The Ignite quick start
Hi Jeremy
thanks for your response. ill take a look at the scan reports. To be more
specific we are running into the following issue
We are using Ignite standalone, from https://ignite.apache.org/download.cgi,
version 2.16.0. We are using thin client to connect to Ignite. When running
Ignite
Apache Ignite release notes contain details about fixes including CVEs
addressed.
https://github.com/apache/ignite/blob/master/RELEASE_NOTES.txt
Current known vulnerabilities are determined by vulnerability testing,
which differs depending on who (test/scan tool vendor, stakeholder/user)
does
Hi All,
We are trying out Apache Ignite version 2.16.0. I want to know where I can
get information about what vulnerabilities (CVE) got addressed in 2.16.0 as
well as what are the current known vulnerabilities on 2.16 (if any).
Appreciate the help and thanks in advance for your response
Vishy
: mercredi 31 juillet 2024 13:13
À : user@ignite.apache.org
Objet : Re: Ignite cache with custom key : key not found
Well, the quick work around would be to add at least one named field to the
object.
Meanwhile, we'll try to figure out the right way to fix it without breaking
backward compatibil
* mardi 30 juillet 2024 11:16
> *À :* user@ignite.apache.org
> *Objet :* Re: Ignite cache with custom key : key not found
>
> Louis, we need to see the code to help you - could you please share it,
> both Java and C++ parts? Ideally a reproducer that we can run.
>
> On Tue, J
>>
>> Louis C.
>> --
>> *De :* Louis C
>> *Envoyé :* lundi 22 juillet 2024 17:06
>> *À :* user@ignite.apache.org
>> *Objet :* RE: Ignite cache with custom key : key not found
>>
>> Hello,
>>
>> Thanks for y
gt;
> Thanks,
>
> Louis C.
> --
> *De :* Louis C
> *Envoyé :* lundi 22 juillet 2024 17:06
> *À :* user@ignite.apache.org
> *Objet :* RE: Ignite cache with custom key : key not found
>
> Hello,
>
> Thanks for your answers.
>
> As for the
Sorry to up this subject, but I have not been able to find a solution/reason
for this problem.
Does anyone have an idea ?
Thanks,
Louis C.
De : Louis C
Envoyé : lundi 22 juillet 2024 17:06
À : user@ignite.apache.org
Objet : RE: Ignite cache with custom key
responding, if we
followhttps://cwiki.apache.org/confluence/display/IGNITE/Binary%20object%20format
to the "Schema Id" which is a "has of the object fields".
In case of C++ thin client it is "00 00 00 00", and "C5 9D 1C 81".
The bytes in position 3 to 4
" from the C++,
>> and when I look at the deserialized keys in the java code, there does not
>> seem to be any difference between the 2 "different" keys, which are both
>> present in the cache.
>>
>> What I saw is that when I do a "
he java code, there does not
> seem to be any difference between the 2 "different" keys, which are both
> present in the cache.
>
> What I saw is that when I do a "Get" from the C++, the key is not
> deserialized (Ignite looks only at the serialized data of the keys)
ook at the deserialized keys in the java code, there does not seem to
be any difference between the 2 "different" keys, which are both present in the
cache.
What I saw is that when I do a "Get" from the C++, the key is not deserialized
(Ignite looks only at the serialize
Hi Ignite Team,
I am working in a Node.js 20 environment and using Ignite 2.16 to
communicate with Ignite via the REST API. My application primarily performs
SQL operations on tables.
While Ignite provides excellent performance when creating and inserting
into one table at a time around (0.2
lot of processing.
If we have that in Ignite 3, we may even be able to get close to
"exactly-once" by starting a transaction on the client, using that
transaction id in a ComputeJob, and then if an exception is bubbled back to
the client, the client can roll back the transaction and start a new o
> how did you discover the answer to this
By enabling "break on all exceptions" in my IDE.
This exception is not logged, Ignite considers this a normal situation,
registers the type automatically and then re-runs the processor.
As Slava said, you should not rely on the fact that
e same. I can test with even earlier
> versions if you'd like.
>
> On Wed, Jul 10, 2024 at 4:08 AM Stephen Darlington
> wrote:
>
>> Do you see the same behaviour with older versions of Ignite, or is this
>> unique to 2.16?
>>
>> On Tue, 9 Jul 2024 at 21:34, Ray
>
> - Raymond
>
> On Thu, Jul 11, 2024 at 8:42 AM Pavel Tupitsyn
> wrote:
>
>> - Duplicate invocation happens due to automatic retry
>> for UnregisteredClassException caused by return value of type
>> LightsaberColor.
>> - Ignite handles the excepti
caused by return value of type
> LightsaberColor.
> - Ignite handles the exception, registers the type automatically, and
> re-runs the processor
> - This only happens once, subsequent invocations are not duplicated
> - To fix this, register the LightsaberColor explicitly in
> Binary
- Duplicate invocation happens due to automatic retry
for UnregisteredClassException caused by return value of type
LightsaberColor.
- Ignite handles the exception, registers the type automatically, and
re-runs the processor
- This only happens once, subsequent invocations are not duplicated
I've only tested the real deal with 2.16, but I just ran the sample repo
test with 2.14, and the output is the same. I can test with even earlier
versions if you'd like.
On Wed, Jul 10, 2024 at 4:08 AM Stephen Darlington
wrote:
> Do you see the same behaviour with older versions of Ign
Do you see the same behaviour with older versions of Ignite, or is this
unique to 2.16?
On Tue, 9 Jul 2024 at 21:34, Raymond Liu wrote:
> Hi all,
>
> We're encountering an issue where entry processors execute twice.
> Executing twice is a problem for us because, for easier opti
://github.com/Philosobyte/ignite
-duplicate-processing-test/blob/main/src/test/java/com/philosobyte/igniteduplicateprocessingtest/DuplicateProcessingTest.java
(in case that link doesn't work, my github username is Philosobyte and the
project is called "ignite-duplicate-processing-test")
Whe
vel,
>
>
>
> How can we achieve Tracing using Ignite .net where Ignite is hosted as
> a .NET service. Could not find any example from .NET perspective.
>
>
>
> https://ignite.apache.org/docs/latest/monitoring-metrics/tracing
>
>
>
> Can we use OpenTel
:
>
> Hi,
>
> I setup a Ignite cluster on docker desktop with the commands and
> default-config.xml provided below;
>
> for ignite-1 node
> docker --context desktop-linux run --name ignite-1 -p 10800:10800 -p
> 11211:11211 -p 47100:47100 -p 47500:47500 -p 49112:49112 -p 8
Hi Pavel,
How can we achieve Tracing using Ignite .net where Ignite is hosted as a
.NET service. Could not find any example from .NET perspective.
https://ignite.apache.org/docs/latest/monitoring-metrics/tracing
Can we use OpenTelemetry Nuget packages which can provide similar
thank you share so good article
Replied Message
From Jeremy McMillan Date 06/21/2024 20:57 To
user@ignite.apache.org Cc Subject Re: [support] ignite tuning help
Also, I didn't look at your network trace screen cap, but you should have zero
TCP retransmissions if you set your initial
STIC transaction and
>>> SERIALIZABLE concurrency mode.
>>>
>>> pseudocode like below
>>> ignite.transactions().txStart
>>> if(acahce.get(key)==null) {
>>> aCahce.put(key,value)
>>> bCahce.put(key,value)
>>> }
>>> tx.com
cy mode.
>>
>> pseudocode like below
>> ignite.transactions().txStart
>> if(acahce.get(key)==null) {
>> aCahce.put(key,value)
>> bCahce.put(key,value)
>> }
>> tx.commit()
>>
>> Sometimes I find aCahce.get(key) costs 80ms ,Sometimes t
t; Sometimes I find aCahce.get(key) costs 80ms ,Sometimes that costs only 5ms.
> and three ignite nodes usage of cpu and io and memory all not high.
> and client node usage of cpu and io and memory all not high.
> but I use tcpdump to find that Between nodes, there are over 40 TCP
> retransmissions per second.
> So is this a network issue?
>
>
like below
ignite.transactions().txStart
if(acahce.get(key)==null) {
aCahce.put(key,value)
bCahce.put(key,value)
}
tx.commit()
Sometimes I find aCahce.get(key) costs 80ms ,Sometimes that costs only 5ms.
and three ignite nodes usage of cpu and io and memory all not high.
and client node usage
CDC not related to Ignite.NET <http://ignite.net/>.
It captures changes that happens on storage (WAL) layer of Ignite.
So, all you need is to follow the examples from documentation and configure CDC
replication.
> 12 июня 2024 г., в 14:02, Pavel Tupitsyn написал(а):
>
> Can
>> > class="org.apache.ignite.configuration.DataRegionConfiguration">
>> > value="Common_Dynamic_Data_Region"/>
>>
>>
>>
i.communication.tcp.TcpCommunicationSpi">
>
>
>
>
>
>
>
> Thanks & Regards,
> Charlin
>
>
>
> On Wed, 12 Jun 2024 at 13:07, Вячеслав Коптилин
> wrote:
>
>> Hi Charlin,
>>
>
> Is this feature available in Ignite .NET ? Can you share the
sample example?
Yes, Continuous Query is available in Ignite.NET, sample code:
https://github.com/apache/ignite/blob/master/modules/platforms/dotnet/examples/Thick/Cache/QueryContinuous/Program.cs
Thanks Pavel.
Is this feature available in Ignite .NET ? Can you share the sample
example?
https://ignite.apache.org/releases/latest/dotnetdoc/api/Apache.Ignite.Core.Cache.Affinity.Rendezvous.ClusterNodeAttributeAffinityBackupFilter.html
Regards
Satyajit
From: Pavel Tupitsyn
Sent
/releases/latest/dotnetdoc/api/Apache.Ignite.Core.Cache.Query.Continuous.ContinuousQuery-2.html
[4]
https://github.com/apache/ignite/blob/master/modules/platforms/dotnet/examples/Thick/Cache/QueryContinuous/Program.cs
On Wed, Jun 12, 2024 at 9:52 AM wrote:
> Hi Pavel,
>
>
>
> How
or the write to complete on all
> participating nodes (primary and backups).
> The second option, that can be used here, is to use 'primary sync' and set
> 'CacheConfiguration#readFromBackup' flag to false. Ignite will always send
> the request to the primary node and get the value from t
Hi All,
I am unable to start a new node (3rd node) which went down some days ago
having 3 node clusters with CacheMode.Partitioned and the 3rd node went
down and unable to join back. Got below error while starting the grid
Got exception while starting(will rollback startup routine).
the write to complete on all
participating nodes (primary and backups).
The second option, that can be used here, is to use 'primary sync' and set
'CacheConfiguration#readFromBackup' flag to false. Ignite will always send
the request to the primary node and get the value from there.
Thanks,
S.
Hi Pavel,
How can we achieve replication from Ignite .NET cluster to another
Ignite .NET cluster as backup using Kafka as middleware? This is needed
for resiliency test for Ignite cluster where we shutdown one cluster and
move all application service to backup
ry rarely).
>
> Ignite version: 2.10
> Cache mode: Partition
> Client : C# with Ignite thick client
>
> Scenario:
> My C# application received a request for cache data insertion @ 09:09:35
> and successfully insertion initiated at application side.
> Thereafter @ 09:10:
a very apparent bug in Ignite, and I don't see anything like
> that in JIRA or release notes.
> Perhaps something else is involved here, another thread or node changing
> the value?
>
> Please prepare a small project that we can run to reproduce the issue.
>
> On Wed, Jun 5, 2024 at 9
> Put and tryget are in two different methods called one after another
That would be a very apparent bug in Ignite, and I don't see anything like
that in JIRA or release notes.
Perhaps something else is involved here, another thread or node changing
the value?
Please prepare a small proj
Hi,
Put and tryget are in two different methods called one after another one
with some time gap based on work flow process
We felt Ignite 2.10 okay for us.
Thanks and Regards
Charlin
On Wed, 5 Jun, 2024, 8:23 pm Pavel Tupitsyn, wrote:
> - Do you run Put and TryGet on the same node?
> -
- Do you run Put and TryGet on the same node?
- Do you have a reproducer?
- Ignite 2.10 was released 3 years ago, have you tried a newer version?
On Wed, Jun 5, 2024 at 3:49 PM Charlin S wrote:
> Hi All,
> I am unable to fetch data from cache by reading by
> key.intermittently (ve
Hi All,
I am unable to fetch data from cache by reading by key.intermittently (very
rarely).
Ignite version: 2.10
Cache mode: Partition
Client : C# with Ignite thick client
Scenario:
My C# application received a request for cache data insertion @ 09:09:35
and successfully insertion initiated
The way that clients operate is quite different in AI3. You can't assume
the same thick/thin distinction.
There are two answers to your question:
1. Ignite 2 will continue to be available. Version 3 is a big update and
it's unlikely that everyone will move over on day 1. So if you like AI2,
it's
Hi Pavel,
Thanks for the quick response.
We are currently evaluating Apache Ignite for our project and are planning
to use features like *CacheEntryProcessor*, *Thick clients with Near
Cache *(Looks
like 3.0 will only have thin clients and near cache is only supported in
thick clients
Amit, unfortunately, I don't have answers at the moment.
I think a JSR107 wrapper can be developed on top of existing Ignite 3 APIs
(Table + Compute), including CacheEntryProcessor support, but we don't have
specific plans for now.
On Fri, May 31, 2024 at 4:34 PM Amit Jolly wrote:
> Hi Pa
Hi Pavel,
Thanks for the quick response.
I had looked at the ignite-3 github repo and could not find any reference
to JSR 107, hence asked this question.
Since Ignite 2.X is fully JSR 107 compliant, now the question is if
ignite-3 is going to be the successor of Ignite 2.X and is going
For now it does not have any of that. KeyValueView [1] is a table access
interface in Ignite 3 that is most similar to a "cache".
https://github.com/apache/ignite-3/blob/main/modules/api/src/main/java/org/apache/ignite/table/KeyValueView.java
On Thu, May 30, 2024 at 6:19 PM Amit Jo
HI,
Will Apache Ignite 3.0 be compliant with JSR107 sepc?
In particular, I am looking at the feature CacheEntryProcessor support in
Ignite 3.0
https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/IgniteCache.html#invoke-K-org.apache.ignite.cache.CacheEntryProcessor
I installed 4 apache ignite nodes on 4 virtual machines that are in a vmware
cluster, one question I have is how do I connect to the cluster? Do I connect
via the IP of any node? Or do I need to put nginx "in front" to do the load
balancing? I didn't find anything about this in th
That's a great article, Ibrahim. Thanks for sharing!
On Thu, 9 May 2024 at 18:00, Ibrahim Altun
wrote:
> Try this post
>
> https://medium.com/segmentify-tech/garbage-collection-g1gc-optimisation-on-apache-ignite-7217f2d9186e
>
>
> <https://www.segmentify.com/>İbr
Try this post
https://medium.com/segmentify-tech/garbage-collection-g1gc-optimisation-on-apache-ignite-7217f2d9186e
<https://www.segmentify.com/>İbrahim Halil AltunExpert R Developer+90 536
3327510 • segmentify.com → <https://www.segmentify.com/>UK • Germany •
Turkey • Spain • P
the solution with appropriate changes to hardware, code,
configuration, and command line options, etc.
Ignite tends to use Java heap mostly for handling query workload. The
slower these queries are, the greater number of them will be running
concurrently. Java heap needs to accommodate the sum of all
The documentation has some good suggestions:
https://ignite.apache.org/docs/latest/perf-and-troubleshooting/memory-tuning#java-heap-and-gc-tuning
On Thu, 9 May 2024 at 07:31, Charlin S wrote:
> Hi All,
>
> I am getting Possible too long JVM pause: 6403 milliseconds. JVM options
> used as below
Hi All,
I am getting Possible too long JVM pause: 6403 milliseconds. JVM options
used as below
-XX:+DisableExplicitGC,-XX:+UseG1GC,-Xms3g,-Xmx5g - client node 1
-XX:+DisableExplicitGC,-XX:+UseG1GC,-Xms1g,-Xmx4g - client node 2
Please suggest this.jvm option to avoid JVM pause issue.
Thanks &
Hi Pavel,
We are observing LongJVMPause count and LongJVMPauseTotalDuration higher on
some nodes compared to other nodes in the cluster. Are we missing any
settings or this is expected behaviour.
Thanks
Satyajit
Barclays Execution Services Limited registered in England.
Hi All ,
We have observed a peculiar case in which ignite shutdown gets stuck
indefinitely
We have deployed ignite 2 nodes in embedded mode.
1. On Node1 , some cache operations are performed which triggers
BinaryMetadata Transfer/sync up with other node
1. This wait
upitsyn,
>> wrote:
>>
>>> Employee class has two fields with the same name:
>>>
>>> [QuerySqlField]
>>> public string EMPCode { get; set; }
>>>
>>> [QuerySqlField]
>>> public string EmpCode { get; set; }
>>>
>>>
>>
error
> 1)
>
> Thanks and Regards,
> Charlin
>
>
> On Wed, 24 Apr, 2024, 4:25 pm Pavel Tupitsyn,
> wrote:
>
>> Employee class has two fields with the same name:
>>
>> [QuerySqlField]
>> public string EMPCode { get; set; }
>>
>> [Quer
MPCode { get; set; }
>
> [QuerySqlField]
> public string EmpCode { get; set; }
>
>
> Ignite 2.10 ignored this and used only one of those for SQL, which may
> lead to subtle bugs. So we added this validation.
>
> You'll have to rename one of the fields, or ove
Employee class has two fields with the same name:
[QuerySqlField]
public string EMPCode { get; set; }
[QuerySqlField]
public string EmpCode { get; set; }
Ignite 2.10 ignored this and used only one of those for SQL, which may lead
to subtle bugs. So we added this validation.
You'll
Hi All,
I am upgrading Ignite from 2.10 to 2.16 and getting Multiple query fields
are associated with the same alias error for *EMPCode* and *EmpName, *which
is working with Ignite 2.10. unable to create Employee cache.
Error 1:
System.Exception: IgniteException for chache :: Employee
Hello
You should give some information otherwise the problem statement is too
generic.
Information such as Ignite version, JVM version, JVM memory parameters, and
Docker deployment resources limits are required.
Cheers
Gianluca
On Sat, 20 Apr 2024 at 10:22, 38797715 <38797...@qq.com>
Hi team,
Start a simple Ignite process using Docker, which is the default
configuration and does nothing. After a period of time, you will find
that the memory occupied by this Ignite process increases until the OOM
Killer is triggered.
If Docker is not used and the Ignite process
Hi Satyajit,
Here you go:
using Apache.Ignite.Core;
using Apache.Ignite.Core.Cache;
using var ignite = Ignition.Start();
var cache = ignite.GetOrCreateCache("myCache");
cache[1] = new Base(1, "base-1");
cache[2] = new Derived(2, "derived-2", 42);
forea
Hi Pavel,
Do we have any working example with Parent and Derived class data model
being saved in Ignite ?.
Regards
Satyajit
Barclays Execution Services Limited registered in England. Registered No.
1767980. Registered office: 1 Churchill Place, London, E14 5HP
Barclays Execution
Hi Satyajit, we (Ignite community members) are subscribed to Stackoverflow
too. I don't have anything to add to the existing answer there.
On Mon, Apr 15, 2024 at 8:09 AM wrote:
> Hi Pavel/Team,
>
>
>
> Is the below explanation holds good from your side. Need some
Hi Pavel/Team,
Is the below explanation holds good from your side. Need some
confirmation on highlighted line in yellow. We are not using Native
persistence. Our cluster is in memory with external cache store enabled.
https://stackoverflow.com/questions/70232020/ignite
Just a reminder that this list is run by volunteers, so we can't guarantee
a response in a given time. Commercial options are available if you need
that.
As for your question: is this the problem?
https://issues.apache.org/jira/browse/IGNITE-16118
On Wed, 3 Apr 2024 at 14:00, Charlin S wrote
Hi All,
could you please help me with this.
Thanks & Regards,
Charlin
On Wed, 27 Mar 2024 at 18:12, Charlin S wrote:
> Hi All,
> We are seeing recently Failed to send TTL update request error in Ignite
> server log. What could be the problem?
> Cache configuration includes :
Environment:
Ignite version: 2.16
HTTP enabled - yes
Logging module - Log4J2
Execution Environment
Containerized -Yes
Base Image : Distroless 12 java
JRE - JRE 17
I am using the Log4j Logging module and set logger for eclipse jetty to
Off/Error, but still
Hi All,
We are seeing recently Failed to send TTL update request error in Ignite
server log. What could be the problem?
Cache configuration includes : EagerTtl = true
Kindly advise on this.
Thanks,
Charlin
wakuntla, Srinivas
> wrote:
>
> Dear Ignite Team,
>
> Hope this email finds your well !
>
> Reaching out to you, as currently we are facing performance issue with Apache
> Ignite. Our application is running on Azure Kubernetes (v1.27.1), which has
> 24 nodes of size &
ed to check all the components of the
> application including Ignite. The good thing is that now I have better
> knowledge of how to troubleshoot issues like this.
>
> My best,
> Alex Avrutin
>
>
> On Fri, Feb 23, 2024 at 10:38 AM Stephen Darlington <
> sdarling.
Stephen,
Thank you for the message. At last, I've found the root cause of the issue.
It was an application bug (expected) but it wasn't the most apparent one.
Out of despair I decided to check all the components of the application
including Ignite. The good thing is that now I have better
>
> My best,
> Alex Avrutin
>
>
> On Thu, Feb 22, 2024 at 3:56 AM Jeremy McMillan <
> jeremy.mcmil...@gridgain.com> wrote:
>
>> First, logging should be configured to at least WARN level if not INFO.
>>
>> Ignite manages data internally at the page le
entirely and re-create it. Tomorrow I'll
check if it helps.
My best,
Alex Avrutin
On Thu, Feb 22, 2024 at 3:56 AM Jeremy McMillan <
jeremy.mcmil...@gridgain.com> wrote:
> First, logging should be configured to at least WARN level if not INFO.
>
> Ignite manages data internally at
First, logging should be configured to at least WARN level if not INFO.
Ignite manages data internally at the page level. If you see errors about
pages, it is low, low level ignite problems. The next level up is
partitions. Errors involving partitions are mid low level ignite problems.
The next
Hello,
A couple of days ago I encountered a strange phenomenon in our application
based on Apache Ignite .Net 2.14 with persistence (3 nodes, 1 backup per
cache).
Data in a cache started disappearing for seemingly no reason and the amount
of records could be halved (220K to 108K) overnight. I
I am running Ignite 2.11.1 with persistence enabled in a 3 node cluster.
After each of the machines were rebooted , one at a time with 4 mins
interval between each reboot , the Ignite client started reporting the
below error while publishing( I am using thick client with datastreamer
I have Ignite Grid (2.11.1) with shutDownPolicy as "GRACEFUL"
I see that when the shutdown hook is invoked , it starts Checkpoint but it
never finishes.
When the Grid is started next time , it prints that checkpointing stopped
in the middle and goes ahead to finish the che
To: user@ignite.apache.org
Subject: Re: Ignite transactions
Hi, Andrey
tx.start() — thread1
cache1.put|get — thread1
cache2.put|get — thread1
tx.commit — thread1
log operation
i didn`t see the problem here
Thanks Pavel!
1. According to business logic, I must transactionally change
I can assume that I can use either queues or a separate thread for
>these purposes.
>
>Нестрогаев Андрей
>
>From: Pavel Tupitsyn < ptupit...@apache.org >
>Sent: Wednesday, February 14, 2024 12:13 PM
>To: user@ignite.apache.org
>Subject: Re: Ignite t
Does anyone have a solution / workaround? We haven’t been able to find an
alternative so far.
Jay
From: Нестрогаев Андрей Викторович
Sent: Wednesday, 14 February 2024 10:41
To: 'user@ignite.apache.org'
Subject: RE: Ignite transactions
1. Perhaps in earlier versions I cou
Subject: RE: Ignite transactions
Thanks Pavel!
1. According to business logic, I must transactionally change the values in
2 caches; in the course of my actions, I must log all these actions in the 3rd
cache (protocol of my actions). So, it doesn’t matter whether my changes in
these first two
@ignite.apache.org
Subject: Re: Ignite transactions
1. Not sure I understand
2. Messaging is not transactional
3. No
4. No, transactions are tied to a specific thread
On Wed, Feb 14, 2024 at 11:01 AM Нестрогаев Андрей Викторович
mailto:a.nestrog...@flexsoft.com>> wrote:
Hi All,
Maybe someo
questions:
>
> 1. How can you organize nested/autonomous transactions in ignite? For
> example, for the purpose of writing a protocol to another cache, so that
> the protocol is saved regardless of the result of the main transaction.
>
> 2. If you use Messaging in ig
Hi All,
Maybe someone has already researched these questions:
1. How can you organize nested/autonomous transactions in ignite? For example,
for the purpose of writing a protocol to another cache, so that the protocol is
saved regardless of the result of the main transaction.
2. If you use
Greetings,
The last update for Ignite 3.0 that I can find is from November of 2022,
although I see the project in GitHub has had continued activity. My team is
looking to start a new project using Ignite, and we were hoping to start with
Ignite 3.0 since this will be a new greenfield project
Subject: Re: Ignite Text Query in .NET
CAUTION: This email originated from outside our organisation -
ptupit...@apache.org<mailto:ptupit...@apache.org> Do not click on links, open
attachments, or respond unless you recognize the sender and can validate the
content is safe.
Hi Satyajit,
Hi Satyajit, looks like the linked stackoverflow page explains it all, I
don't have anything to add.
Pavel
On Mon, Feb 12, 2024 at 4:28 AM wrote:
> Hi Pavel,
>
>
>
> We have observed that when one node went down and we restarted
> the node , Ignite Text query didn’
Hi Pavel,
We have observed that when one node went down and we restarted the
node , Ignite Text query didn't return full set of data. However when we
checked the cache count it was as expected. Is this observation correct
that Lucene index is not copied to RAM
Darlington
Sent: Wednesday, February 7, 2024 12:44 PM
To: user@ignite.apache.org
Subject: Re: ignite + external database
5. Ignite seems to have to know which partitions are lost, and in theory it
doesn’t cost him anything to place these partitions on the remaining nodes
(rebalancing) and execute
>
> 5. Ignite seems to have to know which partitions are lost, and in theory
> it doesn’t cost him anything to place these partitions on the remaining
> nodes (rebalancing) and execute the loadCache for lost partitions.
Yes, Ignite knows which partitions have been lost. "Rese
McMillan
Sent: Wednesday, February 7, 2024 12:28 AM
To: user@ignite.apache.org
Subject: Re: ignite + external database
2. If you want the Ignite cluster to be authoritative about caches, then you
should define them in the XML configuration or deploy your servers with code
which can look up
2. If you want the Ignite cluster to be authoritative about caches, then
you should define them in the XML configuration or deploy your servers with
code which can look up the intended cache configurations and implement
them. If you have specific ideas how you would like to implement this,
maybe
1 - 100 of 10199 matches
Mail list logo
