It’s not really about the volume of transactions, more how likely it is that
multiple clients will be writing to the same records.
https://ignite.apache.org/docs/latest/key-value-api/transactions
> On 3 Nov 2021, at 12:26, Sumit Deshinge wrote:
>
> Thank you Stephen. I will perform the next se
Hi Igniters!
First of all, check the schedule, because we’ve added two more talks that
deserve your attention: https://ignite-summit.org/schedule
Follow Ignite Twitter and LinkedIn for the sneak peeks.
I hope you remember about pre-conference day November 15, 2021, with free
trainings, including
Thank you Stephen. I will perform the next set of runs by adding both
TxTimeoutOnPartitionMapExchange and defaultTxTimeout.
*Also, what is the recommendation for transaction concurrency and isolation
settings for very high frequency transactions with a large number of thin
client connections ?*
disk space is ok
as temp_ignite_libs directory is under /tmp it does not exist anymore :/ my
expectation was by default ignite should have created the directory and
continue the process.
My tests showed that when the cluster is coming up it binds itself to a
specific directory and use it for its wh
Yes. And defaultTxTimeout for similar reasons.
Frankly, these are terrible defaults. There is a ticket to fix the latter:
https://issues.apache.org/jira/browse/IGNITE-13064
> On 3 Nov 2021, at 11:59, Sumit Deshinge wrote:
>
> Hi Ilya,
>
> I have tried to run this with both ignite 2.10 and 2.1
Hi Ilya,
I have tried to run this with both ignite 2.10 and 2.11
There are 24 thin clients on different VMs which are trying to perform
*CRUD* operations on the *same AND/OR different caches* parallelly.
If I set the *TxTimeoutOnPartitionMapExchange *property to some value, then
the transactions s
Out of disk space? The directory /tmp/temp_ignite_libs doesn’t exist?
> On 3 Nov 2021, at 11:26, Ibrahim Altun wrote:
>
> Hi,
>
> We've been using urideploy extension for a long time without any problems,
> but today all of a sudden we seeing following logs on cluster logs;
>
> [2021-11-03T10
Hi,
We've been using urideploy extension for a long time without any problems,
but today all of a sudden we seeing following logs on cluster logs;
[2021-11-03T10:46:20,972][ERROR][grid-uri-scanner-#2-#42][UriDeploymentScannerManager]
Error saving file: cacheentryprocessor-0.0.1-SNAPSHOT.jar
java
The typical way to define the eviction policy would be:
cache.setEvictionPolicyFactory(new LruEvictionPolicyFactory<>(10_000));
To use a lambda, you’d need to deploy the code to the server nodes in advance.
Regards,
Stephen
> On 3 Nov 2021, at 10:02, Vikram Pancholi wrote:
>
> Have you tried to
Have you tried to implement the eviction policy injection without using lambda ?
Also in the cache definitions that work well are you using the same pattern to
set the eviction policy ?
Regards
Vikram Pancholi
> On 3 Nov 2021, at 10.57, Gurmehar Kalra wrote:
>
> cache.setEvictionPolicyFactory
Hi ,
my apologises , here is complete config
cache.setWriteSynchronizationMode(CacheWriteSynchronizationMode.FULL_ASYNC);
cache.setAtomicityMode(CacheAtomicityMode.TRANSACTIONAL);
cache.setCacheMode(CacheMode.REPLICATED);
cache.setGroupName("EngineGroup");
cache.setOnheapCacheEnabl
"LruEvictionPolicy lruEvictionPolicy = *new* LruEvictionPolicy(1); "
Howz this linked to the cache definition you have done ?
BR
On Wed, Nov 3, 2021 at 10:31 AM Gurmehar Kalra
wrote:
> Hi,
>
>
>
> I am getting below stated exception , when trying to run 2 Nodes as server
> ,
> I have around
Hi,
I am getting below stated exception , when trying to run 2 Nodes as server ,
I have around 10 different Caches but exception is coming for 3 Cache only.
I am configuring all cache as
cache.setWriteSynchronizationMode(CacheWriteSynchronizationMode.FULL_ASYNC);
cache.setAtomicityMode(CacheA
I guess so. If vulnerability present in particular JAR by excluding this
JAR from classpath, CVE should not affect you environment.
On 2021/10/27 12:58:12 Dana Milan wrote:
> Hi,
> .
> Can anyone provide a clarification of how jetty is being used by Ignite
> 2.8.1 and whether there is another w
14 matches
Mail list logo
