Thanks for your answer, it answers a part of my question.
But what about this code that is pure C++ ? (can be seen on the previous link I
sent) :
[cid:7fd825a6-4269-4ded-80ea-530ed872a545]
How does one make sure that the server knows this task ?
Best regards,
Louis
С++ client can execute Compute tasks that are written in Java and deployed
to the server nodes:
https://ignite.apache.org/releases/latest/cppdoc/classignite_1_1thin_1_1compute_1_1ComputeClient.html
On Fri, Apr 5, 2024 at 3:41 PM Louis C wrote:
> Hello everyone,
>
> I was interested in the
Hello everyone,
I was interested in the distributed computed in C++ in Ignite, as described
here :
https://ignite.apache.org/docs/latest/distributed-computing/distributed-computing
I noted that the classes that will be executed must be known by the server, as
said here :
In order to run
Hi everyone,
As part of The ASF’s 25th anniversary campaign[1], we will be celebrating
projects and communities in multiple ways.
We invite all projects and contributors to participate in the following
ways:
* Individuals - submit your first contribution:
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 : EagerTtl = true
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
Hello to all users, contributors and Committers!
[ You are receiving this email as a subscriber to one or more ASF project
dev or user
mailing lists and is not being sent to you directly. It is important that
we reach all of our
users and contributors/committers so that they may get a chance
Hi Ronak,
Make sure you don’t have ATOMIC table updates within your transaction.
Thomas
From: Stephen Darlington
Sent: Monday, March 25, 2024 2:31 AM
To: user@ignite.apache.org
Subject: Re: Turning off deadlock detection
This is an EXTERNAL EMAIL. Stop and think before clicking a link or
Just a reminder that this list is run by volunteers. If you need responses
in a given time, commercial options are available.
On Sat, 23 Mar 2024 at 17:50, Ronak Shah wrote:
> Ping again. Can someone answer please? - Ronak
>
> On Mon, Mar 18, 2024 at 12:04 PM Ronak Shah
> wrote:
>
>> Hi Ignite
Thanks Jeremy for the reply. Why does deadlock detection pause all other transaction though for a min? Shouldnt it be a low priority thread job compared to db transactions?RonakOn Mar 24, 2024, at 8:52 PM, Jeremy McMillan
https://ignite.apache.org/docs/latest/key-value-api/transactions#deadlock-detection
The property you're asking about is for diagnostics to enable prevention of
future deadlocks. Turning it off is fine if you already know or can find
out another way what is deadlocked and why.
On Sat, Mar 23,
Ping again. Can someone answer please? - Ronak
On Mon, Mar 18, 2024 at 12:04 PM Ronak Shah
wrote:
> Hi Ignite users,
> I am hitting a situation in a scaled environment where if the transaction
> timeouts for whatever reason, the cluster goes in a deadlock detection
> mode, where it is taking
Hi,
Can we keep SYSTEM_WORKER_TERMINATION in ignoredFailureTypes, is there any
impact. Want to ignore these casting exceptions instead of the server going
down.
2024-03-16T18:37:15,313][ERROR][sys-stripe-56-#57%EDIFCustomerCCNDR%][]
Critical system error detected. Will be handled accordingly
Hi Ignite users,
I am hitting a situation in a scaled environment where if the transaction
timeouts for whatever reason, the cluster goes in a deadlock detection
mode, where it is taking even more time to holding up lock and creating
snowball effect on queued up transactions before going in a
Hi Stephen/Mikhail,
We are getting this issue frequently and bit urgent, server node going out of
the cluster.
Could you please help us.
Thanks,
Gangaiah
From: Gangaiah.Gundeboina.ril.com via user
Sent: 16 March 2024 11:29
To: user@ignite.apache.org
Subject:
Hi,
One of the 8 server node cluster down suddenly, printed error not that much
helpful to find the reason. Given below the log entries, please help us here to
find the reason.
2024-03-16T07:18:52,489][INFO
Hello,
I encountered some errors while trying to build an SQL request and I would
appreciate your input on it.
Using H2 engine, I tried to have a subquery inside a subquery and there is an
exception about unique alias being null.
Something like:
select ... from ( select ... from ( select ...
+ user mailing list
- developer mailing list
This question would be better addressed to the user mailing list.
There are a number of causes of "long JVM pauses,” so it’s difficult to be
prescriptive. I’d start by logging more information about Java’s garbage
collection.
More information in
Hi,
I have a 4 server node cluster with caches are on heap.
Whenever i try to get keys using a scan query or sql field query the heap
usage increases drastically and drops down in few minutes as if both the
queries are loading all respective cache entries as copies in response to
the keys only
Have a look at [1], there is a POC linked [2]
[1] https://www.mail-archive.com/dev@ignite.apache.org/msg53182.html
[2] https://github.com/scottmf/graalvm-ignite
On Fri, Mar 1, 2024 at 8:01 AM Kramer wrote:
> I believe this is not supported with Ignite 2.x due to Native Buffer
> access. It will
I believe this is not supported with Ignite 2.x due to Native Buffer access. It will only be part of Ignite 3 which is still Beta.I haven't tested it myself though, so my comment should be confirmed by others.On 2/29/24, 14:14 Dinakar Devineni wrote:
Hi,
Has anyone tried
You would need to test it to find out.
On Thu, 29 Feb 2024 at 12:03, Dinakar Devineni wrote:
> Does that even work with the newer versions of ignite?
>
>
>
> *From: *Stephen Darlington
> *Sent: *Thursday, February 29, 2024 4:45 AM
> *To: *user@ignite.apache.org
> *Subject: *Re: Control
Hi, Has anyone tried spring native image with ignite? If so is it efficient and what are the pros and cons.Spring Native documentation ThanksDina
Does that even work with the newer versions of ignite? From: Stephen DarlingtonSent: Thursday, February 29, 2024 4:45 AMTo: user@ignite.apache.orgSubject: Re: Control center open source The community used to maintain Web Console. You might be able to get that running again? On Thu, 29 Feb
You can add a filter to your log exporter, so that only the metrics you're
interested in are shared.
"Expensive" might be the wrong word to explain the overhead in enabling
metrics. Enabling metrics does use more resources than not, but it's
usually worth it. In general, you can't put a system
The community used to maintain Web Console. You might be able to get that
running again?
On Thu, 29 Feb 2024 at 04:08, Dinakar Devineni wrote:
> Hi ,
>
> Is there ant grid gain control center open source alternative.
> Is there any other community project?
>
> Thanks
> Dina
>
There's not much overhead simply by enabling SQL, but there's obviously a
cost to maintaining any indexes you create. Normally the cost of
maintaining those indexes is more than offset by improvements in query
performance. But the only real way to tell for your use case is to
benchmark it.
On
Hi,
Regarding new metrics system, when configure to use log exporter, the
metrics are being printed for a cache and again as cache group for the same
cache, even when cache groups are configured? Is it a default behavior, if
so how to fix it, so that only cache metrics are collected.
Also
Hi Team,
Could you please advise if Ignite 2.14/2.15 is vulnerable to
https://spring.io/security/cve-2024-22243 and if so whether a patch is
planned?
Thanks.
Hi ,
Is there ant grid gain control center open source alternative.
Is there any other community project?
Thanks
Dina
Hi, I’m planning to enable and use SQL API for existing Caches by adding all fields are quarriable fields. Will this affect the performance of Key-Value API Cache gets & puts.And are there any side affects, like increased memory usage, reduced performance of cluster using SQL
Glad you got to the bottom of it!
On Sat, 24 Feb 2024 at 00:19, Aleksej Avrutin wrote:
> 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
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
Is there a pattern to the lost records? Is it old records? Records for a
particular customer? Records stored on a specific node or partition?
On Thu, 22 Feb 2024 at 21:14, Aleksej Avrutin wrote:
> Jeremy,
>
> Thank you for the response. I reviewed cache properties using GG Control
> Center and
Jeremy,
Thank you for the response. I reviewed cache properties using GG Control
Center and there was nothing in the cache props that would lead me to the
conclusion that any expiry policy/TTL is set up for the cache. It wasn't
set on the operation level, either.
I decided to delete the cache
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
Ah ok, I understand better.
Thanks for your answer.
On 2024/02/19 11:05:04 Stephen Darlington wrote:
> Ah, the trick you're missing is that the "incr" REST API doesn't (directly)
> use a cache. Instead it uses an Atomic Sequence:
>
Hello to all users, contributors and Committers!
The Travel Assistance Committee (TAC) are pleased to announce that
travel assistance applications for Community over Code Asia 2024 are now
open!
We will be supporting Community over Code Asia, Hangzhou, China
July 26th - 28th, 2024.
TAC exists
Hello Everyone,
When using prometheus to monitor the ignite(ver. 2.13), I cannot find the
parameter ‘sys_memory_nonheap_max’ . It seems that this parameter is available
in the official documentation. How to solve this problem？Thanks.
Tiany Hu，
2024/2/20
Ah, the trick you're missing is that the "incr" REST API doesn't (directly)
use a cache. Instead it uses an Atomic Sequence:
https://ignite.apache.org/docs/latest/data-structures/atomic-types
On Wed, 14 Feb 2024 at 17:38, Louis C wrote:
> Hello,
>
> Thanks for your answers Igor and Stephen.
>
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 checkpointing
Is this
*Env:*
Version of ignite server and thick client : 2.16
Client type: Thick client
*Describe the issue*
1. One cache (data region) used for multiple types of objects viz. standard
Java objects, primitives and User written object (see example below)
2. Cannot use different caches for different
Hello,
Thanks for your answers Igor and Stephen.
Igor, to answer your question to the second point I used the same term as used
in the Rest API[cid:ab48a0d9-3170-457d-a922-c37cacd9171f], but indeed it more
or less what you said (even if in this API we do not have to retrieve
explicitely the
Hi, Zhenya, thanks for the answer
The real cases as this
CASE1
tx.start() — thread1
cache1.put|get — thread1
log operation cache1.put
cache2.put|get — thread1
log operation cache2.put
tx.commit — thread1
all good.
CASE2
tx.start() — thread1
cache1.put|get — thread1
log operation cache1.put
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!
>
>* According to business logic, I must transactionally change the values in 2
>caches; in the course of my actions, I must
> 1. Perhaps in earlier versions I could use the atomic cache to record the
> protocol, …
That’s exactly what we used to do for the exact use case you mentioned.
Unfortunately, this is not possible since atomic cache operations are not
allowed inside transactions anymore.
Does
1. Perhaps in earlier versions I could use the atomic cache to record the
protocol, but in the latest version, using the atomic cache inside a
transaction leads to an error.
Andyrey
From: Нестрогаев Андрей Викторович
Sent: Wednesday, February 14, 2024 12:35 PM
To: user@ignite.apache.org
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 caches end up being a success
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 Нестрогаев Андрей Викторович <
a.nestrog...@flexsoft.com> wrote:
> Hi All,
>
>
>
> Maybe someone has already researched these questions:
>
> 1. How
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
The easy answer to the "50 gets in parallel" is to use GetAll.
On Tue, 13 Feb 2024 at 09:54, Igor Sapego wrote:
> 1. There is no such API. Seems like a weird error in documentation. We
> will fix it. If you want to make 50 gets in parallel, I think it's better
> to run 50 clients with the
1. There is no such API. Seems like a weird error in documentation. We will
fix it. If you want to make 50 gets in parallel, I think it's better to run
50 clients with the current API. You can use the same client too, but it
may be slower, depending on how many nodes you have in a cluster.
2. What
Hi Pavel,
Will it work if we don’t restart the node and cluster is setup with
backup = 1. I mean will lucene index will have backup copy?
Regards
Satyajit
From: Pavel Tupitsyn
Sent: Monday, February 12, 2024 11:36 AM
To: Mandal, Satyajit: IT (PUN)
Cc: user@ignite.apache.org
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’t return full set
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 of
Hello,
I am trying to use/test Apache Ignite for a particular use case. For background
reference, my use case of Ignite is to do 100Ks (to begin with) of "Gets" and
of "increments" of values that will be stored in probably multiple caches in
Apache Ignite.
I read the Ignite documentation, but
Thanks Stephen,
«Given a partition, it's not easy to say which records belong in it»
Is there any recommended sequence of actions to restore the cluster after the
loss of partitions? Should I reload the cache from the database on all nodes
manually again?
Нестрогаев Андрей
From: Stephen
>
> 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. "Reset lost partitions"
Jeremy thanks for your answers and ideas.
5. In my understanding, a cache operating in write-through mode cannot be of
interest of specific client, since it must become the only point of that data
change for all clients, otherwise a data consistency can be in dangers.
Andrey
From: Jeremy
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
2. I understood, You are talking about placing the cache in a persistent data
region and at the same time enabling the read-through, write-through caches
mode.
Thank you. This is, of course, a double penalty, but I’ll think about it and
test this mode.
5. It seems that Ignite has refocused on
For some cache the GetTimeTotal, PutTimeTotal , GetAllTime are only
updating on the client side , so I believe for those particular caches
these are client operations and there are some other cache where the
GetTimeTotal
n all can be seen at both client and server nodes so there i believe these
Thanks Stephen,
2. «You can, actually, enable persistence and connect to a third-party data
store» - is this feature is not the same as using “external database”? coude
you please give the link to the documentation
5. Ignite seems to have to know which partitions are lost, and in theory it
1. With a memory-only cluster, Ignite does not store any persistent
information. You'd need to save your table definitions somewhere yourself
2. If it saved data, it would be a database rather than an in-memory
data grid! You can, actually, enable persistence and connect to a
Most of the metrics are about the node you're talking about rather than the
cluster as a whole. When you're talking about a distributed system, is a
"get" a client or a server operation? A bit of both, right?
On Mon, 29 Jan 2024 at 14:05, Godfather wrote:
> Hi Community ,
> I have configured my
Hi All, I'm trying to use ignite (2.16) as an In-memory data grid (read-through
/ write-through caches), i.e. case described here
https://ignite.apache.org/use-cases/in-memory-data-grid.html
Several questions arose:
1. How is it recommended to store metadata for caches created dynamically
Hello to all users, contributors and Committers!
The Travel Assistance Committee (TAC) are pleased to announce that
travel assistance applications for Community over Code EU 2024 are now
open!
We will be supporting Community over Code EU, Bratislava, Slovakia,
June 3th - 5th, 2024.
TAC exists
Hello to all users, contributors and Committers!
The Travel Assistance Committee (TAC) are pleased to announce that
travel assistance applications for Community over Code EU 2024 are now
open!
We will be supporting Community over Code EU, Bratislava, Slovakia,
June 3th - 5th, 2024.
TAC exists
Hello,
1. Coordinator is the oldest server node. So you can use something
like: ignite.cluster().forServers().forOldest().node()
2. Why can't you upgrade to the new Ignite version? Perhaps this
problem is already fixed. But if not, you can provide details for the
actual Ignite version and this
Hi,
I am running into an issue where rolling deployment of my 5 node cluster is
failing. The issue is repeatable when the 1st node that gets re-deploy is a
coordinator node.
In order to stop this behavior, I want to deploy on coordinator node last.
How can I know which node is a coordinator node?
Hi Community ,
I have configured my application with ignite in client mode.I have a
wrapper around Ignite APIs that provide some out of the box atomic
functionality. I have enabled the cache metrics and after performing some
cache operation I can see that at server node the metrics related to
Great job, Ivan!
On Mon, Jan 29, 2024 at 12:02 PM Ivan Daschinsky
wrote:
> All parsers also have been uploaded to maven central:
>
> https://central.sonatype.com/artifact/org.apache.ignite/ignite-ml-ext/dependents
>
> пн, 29 янв. 2024 г. в 12:00, Ivan Daschinsky :
>
> > The Apache Ignite
Hi, the extension has been released and uploaded to maven central
https://central.sonatype.com/artifact/org.apache.ignite/ignite-ml-ext
вт, 23 янв. 2024 г. в 16:37, Ivan Daschinsky :
> Hi, today I've started voting for the release of ignite-ml-ext 1.0.0. It
> is expected to be released (if
All parsers also have been uploaded to maven central:
https://central.sonatype.com/artifact/org.apache.ignite/ignite-ml-ext/dependents
пн, 29 янв. 2024 г. в 12:00, Ivan Daschinsky :
> The Apache Ignite Community is pleased to announce the release of Apache
> Ignite ML Extension 1.0.0.
>
> You
The Apache Ignite Community is pleased to announce the release of Apache
Ignite ML Extension 1.0.0.
You can download source release here:
https://downloads.apache.org/ignite/ignite-extensions/ignite-ml-ext/1.0.0/
Artifacts can be downloaded from here:
Hi, today I've started voting for the release of ignite-ml-ext 1.0.0. It is
expected to be released (if voting will be successful) in a few days. Stay
tuned.
пн, 22 янв. 2024 г. в 20:53, Stephen Darlington :
> Moving to Java 21 has its own risks, and the chances of you being affected
> by this
Most of your questions are answered in the documentation:
https://ignite.apache.org/docs/latest/configuring-caches/configuring-backups
On Tue, 23 Jan 2024 at 10:52, Patil, Yashodhan wrote:
>
>
> Hi All,
>
>
> We have our application configured with ignite(2.16) in client mode which
> allows us
Hi All,
We have our application configured with ignite(2.16) in client mode which
allows us to communicate with ignite server .
1. I have configured some backups for ignite nodes and I am wondering how
the backup activity works between ignite nodes ?
2. Let's say if I perform any
Moving to Java 21 has its own risks, and the chances of you being affected
by this vulnerability seem pretty low ("This vulnerability does not apply
to Java deployments, typically in servers, that load and run only trusted
code"). In any case, I am told that the ML extension is in the process of
in my case i'm concerned to https://nvd.nist.gov/vuln/detail/CVE-2024-20932
Il giorno lun 22 gen 2024 alle ore 16:11 Stephen Darlington <
sdarling...@apache.org> ha scritto:
> What vulnerability is fixed in Java 21 but not 17?
>
> On Mon, 22 Jan 2024 at 14:30, Angelo Immediata
> wrote:
>
>>
What vulnerability is fixed in Java 21 but not 17?
On Mon, 22 Jan 2024 at 14:30, Angelo Immediata wrote:
> hello Stephen Darlington
> Any news about ignite-ml-ext maven dependency?
> For security reason we upgraded to the openJDK 21 but ignite master node
> (version 2.15) failed to start, so we
hello Stephen Darlington
Any news about ignite-ml-ext maven dependency?
For security reason we upgraded to the openJDK 21 but ignite master node
(version 2.15) failed to start, so we had to upgrade ignite version to the
2.16
Now we have the issue that we canìt find anywhere the machine learning
I agree - with a new project today you should probably start with JDK 21 (LTS) - it has matured for years now.I have also the observation that a couple of third party libraries (eg spring) do not support anymore JDK8 and thus security fixes etc are not provided for those.Am 18.01.2024 um 11:14
Scaping the metrics isn't "free." There's a cost in Ignite to create them
and there's a cost in Prometheus to store them.
It's a good idea to only request those you need.
On Thu, 18 Jan 2024 at 05:08, Godfather wrote:
> Unfortunately we can not switch to OpenCensus.
> And Yes , I have around
Other than the thread that Roman noted, I'm not aware of any specific plans
to move away from Java 8 for Ignite 2.x. As a community-driven project,
there are no guarantees but you'll probably be okay for a year or so.
Worst case, you can build your own Java 8-compatible version.
Having said that,
Unfortunately we can not switch to OpenCensus.
And Yes , I have around 27 cache and I am using jmx-exporter version 0.16.1
.
I noticed that when I use whitelistObjectNames with Mbeans that I want to
scrap then it works blazingly fast (within 1 to 2 seconds !!)
do you recommend using
Hi Stephen, we were planning on implementing Ignite / GridGain in one of our
projects, but we can’t do that if they are going to be dropping Java 8 support
in the next year for example. We are looking for something that will continue
to support Java 8 for the next couple of years at least.
I think the preference would be to use the OpenCensus exporter when using
Prometheus, but the JMX converter should work. Do you have a lot of caches?
I've seen lengthy "scrapes" when there are large numbers of caches.
On Wed, 17 Jan 2024 at 05:14, Godfather wrote:
> Hello Community ,
> I
Max, are you worried that Ignite will or won't drop Java 8 support?
On Tue, 16 Jan 2024 at 17:39, Roman Puchkovskiy
wrote:
> Hi Max.
>
> I'm working at GridGain, so I think the best thing I could do to help
> you is to suggest contacting GridGain representatives, but you already
> did it.
>
>
Hello Community ,
I recently upgraded to ignite 2.16 and the previous problem of jmx metrics
not being exported is now resolved in 2.16 .
However now i am trying to export ignite cache metrics , jmv metrics ,
Partition Map Exchange metrics ,Compute Jobs metrics ,Thread Pools metrics
,
Hi Max.
I'm working at GridGain, so I think the best thing I could do to help
you is to suggest contacting GridGain representatives, but you already
did it.
вт, 16 янв. 2024 г. в 19:21, Max Shultz :
>
> Hi Roman, thanks for the information. Do you know if GridGain is planning on
> having
Hi Roman, thanks for the information. Do you know if GridGain is planning on
having long-term Java 8 support? (I did reach out to them as well, but just
curious if anyone here knows)
Thanks,
- Max
-Original Message-
From: Roman Puchkovskiy
Sent: Tuesday, January 9, 2024 11:50 AM
To:
1. Write-behind mode invokes cache store in background, so there is no
simple way to confirm if a particular write (cache put) has been persisted,
no matter how many backups.
2. AFAIK, cache store is only invoked on the primary node for the given key
On Tue, Jan 9, 2024 at 5:04 PM wrote:
> Hi
Hello,
Unfortunately, SQL does not support TouchedExpiryPolicy. You need to use
KeyValue API to get benefits from it.
Thanks,
S.
пт, 15 дек. 2023 г. в 04:56, 38797715 <38797...@qq.com>:
> From javadoc, An ExpiryPolicy that defines the expiry Duration of a Cache
> Entry based on when it was
Hello,
Yes, scan queries do not honor transaction guarantees.
Thanks,
S.
ср, 27 дек. 2023 г. в 14:43, 38797715 <38797...@qq.com>:
> Hi,
>
> The demo is as follows and attached, It seems that ScanQuery has read the
> intermediate data of the transaction.
>
> Execute the following code:
> @Slf4j
101 - 200 of 31562 matches
Mail list logo
