RE: Transactional Reader Writer Locks

[Gurmehar Kalra]

Hi,

I need to understand when we mean LOCK, is this lock is acquired on entire 
Cache or on record we are trying to update .
Please clarify .

Regards,
Gurmehar Singh

From: Alexei Scherbakov 
Sent: 16 December 2021 22:40
To: user 
Subject: Re: Transactional Reader Writer Locks

[CAUTION: This Email is from outside the Organization. Unless you trust the 
sender, Don't click links or open attachments as it may be a Phishing email, 
which can steal your Information and compromise your Computer.]
Hi.

You can try OPTIMISTIC SERIALIZABLE isolation, it might have better throughput 
in contending scenarios.
But this is not the same as RW lock, because a tx can be invalidated after a 
commit if a lock conflict is detected.
No RW lock of any kind is planned, AFAIK.

вт, 7 дек. 2021 г. в 23:22, mailto:jay.et...@gmx.de>>:
Dear all,

we're running in circles with Ignite for so long now. Can anyone please help? 
All our attempts to custom-build a Reader Writer Lock (/Re-entrant Lock) for 
use inside transactions have failed.

Background:
- Multi-node setup
- Very high throughput mixed read/write cache access
- Key-Value API using transactional caches
- Strong consistency absolute requirement
- Transactional context required for guarantees and fault-tolerance

Using Pessimistic Repeatable-Read transactions gives strong consistency but 
kills performance if there's a large number of operations on the same cache 
entry (and they tend to introduce performance penalties in entire-cache 
operations and difficulties in cross-cache locking as well). All other 
transactional modes somehow violate the strong consistency requirement as we 
see it and were able to test so far.

In other distributed environments we use reader writer locks to gain both 
strong consistency and high performance with mixed workloads. In Ignite however 
we're not aware that explicit locks can be used inside transactions: The 
documentation clearly states so 
(https://ignite.apache.org/docs/latest/distributed-locks)
 and trying to custom-build a reader writer lock for use inside transactions we 
always end up concluding that this may not be achievable if there are multiple 
ways to implicitly acquire but none to release locks.

Are we out of luck here or
- did we miss something?
- are there workarounds you know of?
- are there plans to implement transactional re-entrant locks in future 
releases?

Jay




--

Best regards,
Alexei Scherbakov
::DISCLAIMER::

The contents of this e-mail and any attachment(s) are confidential and intended 
for the named recipient(s) only. E-mail transmission is not guaranteed to be 
secure or error-free as information could be intercepted, corrupted, lost, 
destroyed, arrive late or incomplete, or may contain viruses in transmission. 
The e mail and its contents (with or without referred errors) shall therefore 
not attach any liability on the originator or HCL or its affiliates. Views or 
opinions, if any, presented in this email are solely those of the author and 
may not necessarily reflect the views or opinions of HCL or its affiliates. Any 
form of reproduction, dissemination, copying, disclosure, modification, 
distribution and / or publication of this message without the prior written 
consent of authorized representative of HCL is strictly prohibited. If you have 
received this email in error please delete it and notify the sender 
immediately. Before opening any email and/or attachments, please check them for 
viruses and other defects.

RE: Ignite Cluster Config Issue

[Gurmehar Kalra]

Hi,
Issue got resolved after adding below line of code.

ignite.cluster().baselineAutoAdjustEnabled(true);
ignite.cluster().baselineAutoAdjustTimeout(1);

Regards,
Gurmehar Singh

From: Gurmehar Kalra 
Sent: 25 November 2021 23:08
To: andrei ; user@ignite.apache.org
Subject: RE: Ignite Cluster Config Issue

[CAUTION: This Email is from outside the Organization. Unless you trust the 
sender, Don’t click links or open attachments as it may be a Phishing email, 
which can steal your Information and compromise your Computer.]
Hi,

I am not deploying any explicit service.
My Question here is if I am  running 2 server nodes then both should be able to 
read and write to Ignite, where as in current condition only one  application 
is able to read from ignite .
Ignite jar are part of Spring application which are deployed on 2 different 
Machines.

Below is Piece of code which is running on one machine and not on other


Lock _lock =null;
 try {
_lock = 
CacheManager.getLock("DSLOCK", JourneyCacheEnum.IGNITE_DS_CACHE);
 _lock.lock();
ScanQuery scanQuery = new ScanQuery<>(
   new 
IgniteBiPredicate() {

  private static final long serialVersionUID = 1L;

  @Override

  public boolean apply(String e1, DecisionSplitWait e2) {

 Instant timeLapse = e2.getTimeLapse();

 return ObjectUtils.isEmpty(timeLapse) ? true

   : 
timeLapse.isBefore(Instant.now());

  }
   });

scanQuery.setPageSize(1);

QueryCursor> cursor = 
CacheManager.query(scanQuery, JourneyCacheEnum.IGNITE_DS_CACHE);
  
Iterator> iterator = cursor.iterator();
Entry entry = null;
if 
(iterator.hasNext()) {
   
entry = iterator.next();
}
if 
(!ObjectUtils.isEmpty(entry)) {
   key 
= entry.getKey();
   
decisionSplitWait = entry.getValue();

decisionSplitWait.setTimeLapse(Instant.now().plusSeconds(WAIT_TIME_ADDED_FOR_SCAN));
   
CacheManager.getAndReplace(key, decisionSplitWait, 
JourneyCacheEnum.IGNITE_DS_CACHE);
}
 }finally {
  if(!ObjectUtils.isEmpty(_lock)) {
_lock.unlock();
  }
}

Regards,
Gurmehar Singh

From: andrei mailto:aealexsand...@gmail.com>>
Sent: 25 November 2021 16:48
To: Gurmehar Kalra mailto:gurmehar.ka...@hcl.com>>; 
user@ignite.apache.org<mailto:user@ignite.apache.org>
Subject: Re: Ignite Cluster Config Issue

[CAUTION: This Email is from outside the Organization. Unless you trust the 
sender, Don’t click links or open attachments as it may be a Phishing email, 
which can steal your Information and compromise your Computer.]

Hi,

I think you have a singleton service that has been deployed to a random Ignite 
server node. Try checking your service configuration and make sure it contains 
at least the following:

 svcCfg.setMaxPerNodeCount(1);

 svcCfg.setTotalCount(3);
With these properties, you will have one instance of the service across three 
nodes. And your service was deployed as:

ig.services(ig.cluster().forServers());

Regards,
Andrei

11/25/2021 2:01 PM, Gurmehar Kalra пишет:
Hey,

Let me explain Architecture

I am running 3 Ignite server nodes  ,each have some services  which 

RE: Ignite Cluster Config Issue

[Gurmehar Kalra]

Hi,

I am not deploying any explicit service.
My Question here is if I am  running 2 server nodes then both should be able to 
read and write to Ignite, where as in current condition only one  application 
is able to read from ignite .
Ignite jar are part of Spring application which are deployed on 2 different 
Machines.

Below is Piece of code which is running on one machine and not on other


Lock _lock =null;
 try {
_lock = 
CacheManager.getLock("DSLOCK", JourneyCacheEnum.IGNITE_DS_CACHE);
 _lock.lock();
ScanQuery scanQuery = new ScanQuery<>(
   new 
IgniteBiPredicate() {

  private static final long serialVersionUID = 1L;

  @Override

  public boolean apply(String e1, DecisionSplitWait e2) {

 Instant timeLapse = e2.getTimeLapse();

 return ObjectUtils.isEmpty(timeLapse) ? true

   : 
timeLapse.isBefore(Instant.now());

  }
   });

scanQuery.setPageSize(1);

QueryCursor> cursor = 
CacheManager.query(scanQuery, JourneyCacheEnum.IGNITE_DS_CACHE);
  
Iterator> iterator = cursor.iterator();
Entry entry = null;
if 
(iterator.hasNext()) {
   
entry = iterator.next();
}
if 
(!ObjectUtils.isEmpty(entry)) {
   key 
= entry.getKey();
   
decisionSplitWait = entry.getValue();

decisionSplitWait.setTimeLapse(Instant.now().plusSeconds(WAIT_TIME_ADDED_FOR_SCAN));
   
CacheManager.getAndReplace(key, decisionSplitWait, 
JourneyCacheEnum.IGNITE_DS_CACHE);
}
 }finally {
  if(!ObjectUtils.isEmpty(_lock)) {
_lock.unlock();
  }
}

Regards,
Gurmehar Singh

From: andrei 
Sent: 25 November 2021 16:48
To: Gurmehar Kalra ; user@ignite.apache.org
Subject: Re: Ignite Cluster Config Issue

[CAUTION: This Email is from outside the Organization. Unless you trust the 
sender, Don’t click links or open attachments as it may be a Phishing email, 
which can steal your Information and compromise your Computer.]

Hi,

I think you have a singleton service that has been deployed to a random Ignite 
server node. Try checking your service configuration and make sure it contains 
at least the following:

 svcCfg.setMaxPerNodeCount(1);

 svcCfg.setTotalCount(3);
With these properties, you will have one instance of the service across three 
nodes. And your service was deployed as:

ig.services(ig.cluster().forServers());

Regards,
Andrei

11/25/2021 2:01 PM, Gurmehar Kalra пишет:
Hey,

Let me explain Architecture

I am running 3 Ignite server nodes  ,each have some services  which read and 
write data from Kafka and also to Ignite
all services(From all servers ) are able to read from kafka and  publish it to 
Ignite.(Ignite is in replication mode).
But the thread responsible for reading from Ignite are only working on Single 
Node.
I have added IP in Logs to identify , which packet is read from which IP .
In logs it clearly shows that all services from all Nodes are able to write to 
Ignite , but only Single Node is reading it and publishing it ahead .

Regards,
Gurmehar Singh

From: andrei <mailto:aealexsand...@gmail.com>
Sent: 25 November 2021 16:17
To: user@ignite.apache.org<mailto:user@ignite.apache.org>

RE: Ignite Cluster Config Issue

[Gurmehar Kalra]

Hey,

Let me explain Architecture

I am running 3 Ignite server nodes  ,each have some services  which read and 
write data from Kafka and also to Ignite
all services(From all servers ) are able to read from kafka and  publish it to 
Ignite.(Ignite is in replication mode).
But the thread responsible for reading from Ignite are only working on Single 
Node.
I have added IP in Logs to identify , which packet is read from which IP .
In logs it clearly shows that all services from all Nodes are able to write to 
Ignite , but only Single Node is reading it and publishing it ahead .

Regards,
Gurmehar Singh

From: andrei 
Sent: 25 November 2021 16:17
To: user@ignite.apache.org
Subject: Re: Ignite Cluster Config Issue

[CAUTION: This Email is from outside the Organization. Unless you trust the 
sender, Don’t click links or open attachments as it may be a Phishing email, 
which can steal your Information and compromise your Computer.]

Hey,

Sorry, but I don't understand what the issue you mentioned? You are using a 
transaction cache and most likely using transactions. Perhaps you are just 
having design problems. Tell us more about what you are going to achieve.

Sincerely,
Andrey
11/25/2021 11:24 AM, Gurmehar Kalra пишет:
Hi,

Team stuck with Issue with in Ignite Cluster where in Only Single Node is able 
to read data from Ignite ,other Nodes are able to write data on to Ignite , 
data is shared with other Nodes,
Below is configuration

cache.setWriteSynchronizationMode(CacheWriteSynchronizationMode.FULL_ASYNC);
cache.setAtomicityMode(CacheAtomicityMode.TRANSACTIONAL);
cache.setCacheMode(CacheMode.REPLICATED);
cache.setGroupName("EngineGroup");
cache.setOnheapCacheEnabled(true);

  LruEvictionPolicyFactory lruEvictionPolicyFactory = new 
LruEvictionPolicyFactory<>(1);
  lruEvictionPolicyFactory.create();
  cache.setEvictionPolicyFactory(lruEvictionPolicyFactory);


TCP/IP Discovery Code
TcpDiscoveryVmIpFinder ipFinder = new TcpDiscoveryVmIpFinder();
  ipFinder.setShared(true);
  ipFinder.setAddresses(
  Lists.newArrayList(IP1,IP2,IP3));
  tcpDiscoverySpi.setIpFinder(ipFinder);

All help appreciated .
Regards,
Gurmehar Singh

::DISCLAIMER::

The contents of this e-mail and any attachment(s) are confidential and intended 
for the named recipient(s) only. E-mail transmission is not guaranteed to be 
secure or error-free as information could be intercepted, corrupted, lost, 
destroyed, arrive late or incomplete, or may contain viruses in transmission. 
The e mail and its contents (with or without referred errors) shall therefore 
not attach any liability on the originator or HCL or its affiliates. Views or 
opinions, if any, presented in this email are solely those of the author and 
may not necessarily reflect the views or opinions of HCL or its affiliates. Any 
form of reproduction, dissemination, copying, disclosure, modification, 
distribution and / or publication of this message without the prior written 
consent of authorized representative of HCL is strictly prohibited. If you have 
received this email in error please delete it and notify the sender 
immediately. Before opening any email and/or attachments, please check them for 
viruses and other defects.

Ignite Cluster Config Issue

[Gurmehar Kalra]

Hi,

Team stuck with Issue with in Ignite Cluster where in Only Single Node is able 
to read data from Ignite ,other Nodes are able to write data on to Ignite , 
data is shared with other Nodes,
Below is configuration

cache.setWriteSynchronizationMode(CacheWriteSynchronizationMode.FULL_ASYNC);
cache.setAtomicityMode(CacheAtomicityMode.TRANSACTIONAL);
cache.setCacheMode(CacheMode.REPLICATED);
cache.setGroupName("EngineGroup");
cache.setOnheapCacheEnabled(true);

  LruEvictionPolicyFactory lruEvictionPolicyFactory = new 
LruEvictionPolicyFactory<>(1);
  lruEvictionPolicyFactory.create();
  cache.setEvictionPolicyFactory(lruEvictionPolicyFactory);


TCP/IP Discovery Code
TcpDiscoveryVmIpFinder ipFinder = new TcpDiscoveryVmIpFinder();
  ipFinder.setShared(true);
  ipFinder.setAddresses(
  Lists.newArrayList(IP1,IP2,IP3));
  tcpDiscoverySpi.setIpFinder(ipFinder);

All help appreciated .
Regards,
Gurmehar Singh

::DISCLAIMER::

The contents of this e-mail and any attachment(s) are confidential and intended 
for the named recipient(s) only. E-mail transmission is not guaranteed to be 
secure or error-free as information could be intercepted, corrupted, lost, 
destroyed, arrive late or incomplete, or may contain viruses in transmission. 
The e mail and its contents (with or without referred errors) shall therefore 
not attach any liability on the originator or HCL or its affiliates. Views or 
opinions, if any, presented in this email are solely those of the author and 
may not necessarily reflect the views or opinions of HCL or its affiliates. Any 
form of reproduction, dissemination, copying, disclosure, modification, 
distribution and / or publication of this message without the prior written 
consent of authorized representative of HCL is strictly prohibited. If you have 
received this email in error please delete it and notify the sender 
immediately. Before opening any email and/or attachments, please check them for 
viruses and other defects.

RE: Exception for Eviction Policy on Selected Cache

[Gurmehar Kalra]

Hi ,

my apologises , here is complete config
cache.setWriteSynchronizationMode(CacheWriteSynchronizationMode.FULL_ASYNC);
cache.setAtomicityMode(CacheAtomicityMode.TRANSACTIONAL);
cache.setCacheMode(CacheMode.REPLICATED);
cache.setGroupName("EngineGroup");
cache.setOnheapCacheEnabled(true);
LruEvictionPolicy lruEvictionPolicy = new LruEvictionPolicy(1);

cache.setEvictionPolicyFactory(()-> lruEvictionPolicy);

Regards,
Gurmehar Singh

From: Vikram Pancholi 
Sent: 03 November 2021 15:11
To: user@ignite.apache.org
Subject: Re: Exception for Eviction Policy on Selected Cache

[CAUTION: This Email is from outside the Organization. Unless you trust the 
sender, Don’t click links or open attachments as it may be a Phishing email, 
which can steal your Information and compromise your Computer.]
"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 
mailto:gurmehar.ka...@hcl.com>> wrote:
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(CacheAtomicityMode.TRANSACTIONAL);
cache.setCacheMode(CacheMode.REPLICATED);
cache.setGroupName("EngineGroup");
cache.setOnheapCacheEnabled(true);
LruEvictionPolicy lruEvictionPolicy = new LruEvictionPolicy(1);

Caused by: org.apache.ignite.IgniteException: Eviction policy factory mismatch 
[cacheName=journeyDelayUtilityCacheV2, 
localEvictionPolicyFactory=com.hcl.journey.cache.config.IgniteConfig$$Lambda$414/452368204,
 
remoteEvictionPolicyFactory=com.hcl.journey.cache.config.IgniteConfig$$Lambda$414/214405279,
 rmtNodeId=834a36bb-b4e9-45bd-b0a9-95d346c9de7f] Fix cache configuration or set 
system property -DIGNITE_SKIP_CONFIGURATION_CONSISTENCY_CHECK=true.

Please suggest.

Regards,
Gurmehar Singh

::DISCLAIMER::

The contents of this e-mail and any attachment(s) are confidential and intended 
for the named recipient(s) only. E-mail transmission is not guaranteed to be 
secure or error-free as information could be intercepted, corrupted, lost, 
destroyed, arrive late or incomplete, or may contain viruses in transmission. 
The e mail and its contents (with or without referred errors) shall therefore 
not attach any liability on the originator or HCL or its affiliates. Views or 
opinions, if any, presented in this email are solely those of the author and 
may not necessarily reflect the views or opinions of HCL or its affiliates. Any 
form of reproduction, dissemination, copying, disclosure, modification, 
distribution and / or publication of this message without the prior written 
consent of authorized representative of HCL is strictly prohibited. If you have 
received this email in error please delete it and notify the sender 
immediately. Before opening any email and/or attachments, please check them for 
viruses and other defects.

Exception for Eviction Policy on Selected Cache

[Gurmehar Kalra]

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(CacheAtomicityMode.TRANSACTIONAL);
cache.setCacheMode(CacheMode.REPLICATED);
cache.setGroupName("EngineGroup");
cache.setOnheapCacheEnabled(true);
LruEvictionPolicy lruEvictionPolicy = new LruEvictionPolicy(1);

Caused by: org.apache.ignite.IgniteException: Eviction policy factory mismatch 
[cacheName=journeyDelayUtilityCacheV2, 
localEvictionPolicyFactory=com.hcl.journey.cache.config.IgniteConfig$$Lambda$414/452368204,
 
remoteEvictionPolicyFactory=com.hcl.journey.cache.config.IgniteConfig$$Lambda$414/214405279,
 rmtNodeId=834a36bb-b4e9-45bd-b0a9-95d346c9de7f] Fix cache configuration or set 
system property -DIGNITE_SKIP_CONFIGURATION_CONSISTENCY_CHECK=true.

Please suggest.

Regards,
Gurmehar Singh

::DISCLAIMER::

The contents of this e-mail and any attachment(s) are confidential and intended 
for the named recipient(s) only. E-mail transmission is not guaranteed to be 
secure or error-free as information could be intercepted, corrupted, lost, 
destroyed, arrive late or incomplete, or may contain viruses in transmission. 
The e mail and its contents (with or without referred errors) shall therefore 
not attach any liability on the originator or HCL or its affiliates. Views or 
opinions, if any, presented in this email are solely those of the author and 
may not necessarily reflect the views or opinions of HCL or its affiliates. Any 
form of reproduction, dissemination, copying, disclosure, modification, 
distribution and / or publication of this message without the prior written 
consent of authorized representative of HCL is strictly prohibited. If you have 
received this email in error please delete it and notify the sender 
immediately. Before opening any email and/or attachments, please check them for 
viruses and other defects.

Ignite Stopping Abruptly

[Gurmehar Kalra]

Hi,

Using Apache Ignite 2.10, with config as

cache.setWriteSynchronizationMode(CacheWriteSynchronizationMode.FULL_ASYNC);
cache.setAtomicityMode(CacheAtomicityMode.TRANSACTIONAL);
cache.setCacheMode(CacheMode.REPLICATED);
cache.setGroupName("EngineGroup");
cache.setOnheapCacheEnabled(true);
cache.setEvictionPolicyFactory(()-> new LruEvictionPolicy(1));

There are 2 cache which have TTL enabled
kafkaCacheError.setExpiryPolicyFactory(CreatedExpiryPolicy.factoryOf(Duration.TWENTY_MINUTES));
kafkaCacheError.setEagerTtl(true);

ignite give intermittent error
'Possible failure suppressed accordingly to a configured handler 
[hnd=StopNodeOrHaltFailureHandler [tryStop=false, timeout=0, 
super=AbstractFailureHandler [ignoredFailureTypes=UnmodifiableSet 
[SYSTEM_WORKER_BLOCKED, SYSTEM_CRITICAL_OPERATION_TIMEOUT]]], 
failureCtx=FailureContext [type=SYSTEM_WORKER_BLOCKED, err=class 
o.a.i.IgniteException: GridWorker [name=ttl-cleanup-worker, 
igniteInstanceName=journeyengine, finished=false, heartbeatTs=1625507061348]]]

after sometime of this error ignite stops .

Please suggest

Regards,
Gurmehar Singh

::DISCLAIMER::

The contents of this e-mail and any attachment(s) are confidential and intended 
for the named recipient(s) only. E-mail transmission is not guaranteed to be 
secure or error-free as information could be intercepted, corrupted, lost, 
destroyed, arrive late or incomplete, or may contain viruses in transmission. 
The e mail and its contents (with or without referred errors) shall therefore 
not attach any liability on the originator or HCL or its affiliates. Views or 
opinions, if any, presented in this email are solely those of the author and 
may not necessarily reflect the views or opinions of HCL or its affiliates. Any 
form of reproduction, dissemination, copying, disclosure, modification, 
distribution and / or publication of this message without the prior written 
consent of authorized representative of HCL is strictly prohibited. If you have 
received this email in error please delete it and notify the sender 
immediately. Before opening any email and/or attachments, please check them for 
viruses and other defects.

RE: Ignite Cluster Issue on 2.7.6

[Gurmehar Kalra]

Hi,

Below are the logs
BaselineTopology of joining node (e6d542e7-cd73-4e57-90c1-b28da508c2c6) is not 
compatible with BaselineTopology in the cluster. Branching history of cluster 
BlT ([1016056908]) doesn't contain branching point hash of joining node BlT 
(510622971). Consider cleaning persistent storage of the node and adding it to 
the cluster again.
   at 
org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.checkFailedError(TcpDiscoverySpi.java:1946)
 ~[ignite-core-2.7.6.jar:2.7.6]
   at 
org.apache.ignite.spi.discovery.tcp.ServerImpl.joinTopology(ServerImpl.java:969)
 ~[ignite-core-2.7.6.jar:2.7.6]
   at 
org.apache.ignite.spi.discovery.tcp.ServerImpl.spiStart(ServerImpl.java:391) 
~[ignite-core-2.7.6.jar:2.7.6]
   at 
org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.spiStart(TcpDiscoverySpi.java:2020)
 ~[ignite-core-2.7.6.jar:2.7.6]
   at 
org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManagerAdapter.java:297)
 ~[ignite-core-2.7.6.jar:2.7.6]
   ... 52 common frames omitted

Regards,
Gurmehar Singh

From: Gurmehar Kalra 
Sent: 04 November 2020 13:34
To: user@ignite.apache.org
Cc: Andrei Aleksandrov 
Subject: RE: Ignite Cluster Issue on 2.7.6

[CAUTION: This Email is from outside the Organization. Unless you trust the 
sender, Don’t click links or open attachments as it may be a Phishing email, 
which can steal your Information and compromise your Computer.]
Hi,
 I did not remove the code ignite.cluster().active(true) , however added 
condition on one application to check if cluster is active or not and the other 
application activates the cluster.

Regards,
Gurmehar Singh

From: Andrei Aleksandrov 
mailto:aealexsand...@gmail.com>>
Sent: 30 October 2020 20:01
To: user@ignite.apache.org<mailto:user@ignite.apache.org>
Subject: Re: Ignite Cluster Issue on 2.7.6

[CAUTION: This Email is from outside the Organization. Unless you trust the 
sender, Don’t click links or open attachments as it may be a Phishing email, 
which can steal your Information and compromise your Computer.]

Hi,

Did you remove the code with ignite.cluster().active(true); ?
However, yes, all of your data nodes should be in baseline topology. Could you 
collect logs from your servers?

BR,
Andrei
10/30/2020 2:28 PM, Gurmehar Kalra пишет:
Hi,

I tried changes suggested by you , waited for nodes  and then tried to start 
cluster , but only 1 node is  joins cluster other node  does not participates 
in cluster.
Do I have to add all nodes into BLT ?
Regards,
Gurmehar Singh

From: Andrei Aleksandrov 
<mailto:aealexsand...@gmail.com>
Sent: 29 October 2020 20:11
To: user@ignite.apache.org<mailto:user@ignite.apache.org>
Subject: Re: Ignite Cluster Issue on 2.7.6

[CAUTION: This Email is from outside the Organization. Unless you trust the 
sender, Don’t click links or open attachments as it may be a Phishing email, 
which can steal your Information and compromise your Computer.]

Hi,

Do you use cluster with persistence? After first actication all your data will 
be located on the first activated node.

In this case, you also should track your baseline.

https://www.gridgain.com/docs/latest/developers-guide/baseline-topology<https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.gridgain.com%2Fdocs%2Flatest%2Fdevelopers-guide%2Fbaseline-topology&data=04%7C01%7Cgurmehar.kalra%40hcl.com%7Cc975b5cbb3cf4d88ca6708d880984c02%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0%7C637400738885440196%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=UIwjsZUzz2LQZfeSIFYL4zg3ybWNNEFfnBWXFm7TY8I%3D&reserved=0>

Baseline topology is a subset of nodes where you cache data located.

The recommendations are the following:

1)you should activate the cluster only when all server nodes were started
2)If the topology changes, you must either restore the failed nodes or reset to 
the base topology to trigger partition reassignment and rebalancing.
3)If some new node should contain the cache data then you should add this node 
to baseline topology:

using java code:

https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/IgniteCluster.html#setBaselineTopology-java.util.Collection<https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fignite.apache.org%2Freleases%2Flatest%2Fjavadoc%2Forg%2Fapache%2Fignite%2FIgniteCluster.html%23setBaselineTopology-java.util.Collection&data=04%7C01%7Cgurmehar.kalra%40hcl.com%7Cc975b5cbb3cf4d88ca6708d880984c02%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0%7C637400738885440196%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=hsqjATck%2Fbd8lDmS%2BF%2Femhc5yCb5kSFCGQcYu3fvRmU%3D&reserved=0>-

using utility tool:

https://www.gridgain.com/docs/latest/administrators-guide/control-script#adding-nodes-to-baseline-topology<https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.

RE: Ignite Cluster Issue on 2.7.6

[Gurmehar Kalra]

Hi,
 I did not remove the code ignite.cluster().active(true) , however added 
condition on one application to check if cluster is active or not and the other 
application activates the cluster.

Regards,
Gurmehar Singh

From: Andrei Aleksandrov 
Sent: 30 October 2020 20:01
To: user@ignite.apache.org
Subject: Re: Ignite Cluster Issue on 2.7.6

[CAUTION: This Email is from outside the Organization. Unless you trust the 
sender, Don’t click links or open attachments as it may be a Phishing email, 
which can steal your Information and compromise your Computer.]

Hi,

Did you remove the code with ignite.cluster().active(true); ?
However, yes, all of your data nodes should be in baseline topology. Could you 
collect logs from your servers?

BR,
Andrei
10/30/2020 2:28 PM, Gurmehar Kalra пишет:
Hi,

I tried changes suggested by you , waited for nodes  and then tried to start 
cluster , but only 1 node is  joins cluster other node  does not participates 
in cluster.
Do I have to add all nodes into BLT ?
Regards,
Gurmehar Singh

From: Andrei Aleksandrov 
<mailto:aealexsand...@gmail.com>
Sent: 29 October 2020 20:11
To: user@ignite.apache.org<mailto:user@ignite.apache.org>
Subject: Re: Ignite Cluster Issue on 2.7.6

[CAUTION: This Email is from outside the Organization. Unless you trust the 
sender, Don’t click links or open attachments as it may be a Phishing email, 
which can steal your Information and compromise your Computer.]

Hi,

Do you use cluster with persistence? After first actication all your data will 
be located on the first activated node.

In this case, you also should track your baseline.

https://www.gridgain.com/docs/latest/developers-guide/baseline-topology<https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.gridgain.com%2Fdocs%2Flatest%2Fdevelopers-guide%2Fbaseline-topology&data=04%7C01%7Cgurmehar.kalra%40hcl.com%7C22ef28f5374d48a899f208d87ce06b4e%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0%7C637396650601669318%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=jSjcT09Vo8s5xhGt1tsSGc9sGAObsfnUyoxII14X3bA%3D&reserved=0>

Baseline topology is a subset of nodes where you cache data located.

The recommendations are the following:

1)you should activate the cluster only when all server nodes were started
2)If the topology changes, you must either restore the failed nodes or reset to 
the base topology to trigger partition reassignment and rebalancing.
3)If some new node should contain the cache data then you should add this node 
to baseline topology:

using java code:

https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/IgniteCluster.html#setBaselineTopology-java.util.Collection<https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fignite.apache.org%2Freleases%2Flatest%2Fjavadoc%2Forg%2Fapache%2Fignite%2FIgniteCluster.html%23setBaselineTopology-java.util.Collection&data=04%7C01%7Cgurmehar.kalra%40hcl.com%7C22ef28f5374d48a899f208d87ce06b4e%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0%7C637396650601669318%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=g56cjLJ5WSRh95rk%2F9O8iy7oB9CWdcLC1VyZzdSp8j8%3D&reserved=0>-

using utility tool:

https://www.gridgain.com/docs/latest/administrators-guide/control-script#adding-nodes-to-baseline-topology<https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.gridgain.com%2Fdocs%2Flatest%2Fadministrators-guide%2Fcontrol-script%23adding-nodes-to-baseline-topology&data=04%7C01%7Cgurmehar.kalra%40hcl.com%7C22ef28f5374d48a899f208d87ce06b4e%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0%7C637396650601679306%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=LY9iSmFY3QceY2%2FvrOEsH0Qq70EbOhkqiVVV4JwB7ws%3D&reserved=0>

4)In case if some node from baseline can't be started (e.g because its data on 
the disk was destroyed) it should be removed from baseline:

https://www.gridgain.com/docs/latest/administrators-guide/control-script#removing-nodes-from-baseline-topology<https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.gridgain.com%2Fdocs%2Flatest%2Fadministrators-guide%2Fcontrol-script%23removing-nodes-from-baseline-topology&data=04%7C01%7Cgurmehar.kalra%40hcl.com%7C22ef28f5374d48a899f208d87ce06b4e%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0%7C637396650601679306%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=BxnfpdgqtPaqGwEji9B5VqRfDRpH5CUCN6ZRX%2F7r8P8%3D&reserved=0>

If you are not using persistence, please provide additional information that 
"data is being added to the cache but not available to any of the modules." 
means:

1) How you access data
2) What do you see in the logs

BR,
Andrei
10/29/2020 4:19 PM, Gurmehar Kalra пишет:
Hi,

I have two module(Web and Engine)  and want to sha

RE: Ignite Cluster Issue on 2.7.6

[Gurmehar Kalra]

Hi,

I tried changes suggested by you , waited for nodes  and then tried to start 
cluster , but only 1 node is  joins cluster other node  does not participates 
in cluster.
Do I have to add all nodes into BLT ?
Regards,
Gurmehar Singh

From: Andrei Aleksandrov 
Sent: 29 October 2020 20:11
To: user@ignite.apache.org
Subject: Re: Ignite Cluster Issue on 2.7.6

[CAUTION: This Email is from outside the Organization. Unless you trust the 
sender, Don’t click links or open attachments as it may be a Phishing email, 
which can steal your Information and compromise your Computer.]

Hi,

Do you use cluster with persistence? After first actication all your data will 
be located on the first activated node.

In this case, you also should track your baseline.

https://www.gridgain.com/docs/latest/developers-guide/baseline-topology<https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.gridgain.com%2Fdocs%2Flatest%2Fdevelopers-guide%2Fbaseline-topology&data=04%7C01%7Cgurmehar.kalra%40hcl.com%7Cb6b965fa945e4a7f9b2608d87c189df1%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0%7C637395793215914323%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=vlUsoU0O2U8cW1aqojX29MmnxvhnVfL%2B4AbVGem5wIs%3D&reserved=0>

Baseline topology is a subset of nodes where you cache data located.

The recommendations are the following:

1)you should activate the cluster only when all server nodes were started
2)If the topology changes, you must either restore the failed nodes or reset to 
the base topology to trigger partition reassignment and rebalancing.
3)If some new node should contain the cache data then you should add this node 
to baseline topology:

using java code:

https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/IgniteCluster.html#setBaselineTopology-java.util.Collection<https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fignite.apache.org%2Freleases%2Flatest%2Fjavadoc%2Forg%2Fapache%2Fignite%2FIgniteCluster.html%23setBaselineTopology-java.util.Collection&data=04%7C01%7Cgurmehar.kalra%40hcl.com%7Cb6b965fa945e4a7f9b2608d87c189df1%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0%7C637395793215914323%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=i470Z%2FOz7uOPcm8dgQXSJYNhrlUXfcv6fTn%2BQlnfeVk%3D&reserved=0>-

using utility tool:

https://www.gridgain.com/docs/latest/administrators-guide/control-script#adding-nodes-to-baseline-topology<https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.gridgain.com%2Fdocs%2Flatest%2Fadministrators-guide%2Fcontrol-script%23adding-nodes-to-baseline-topology&data=04%7C01%7Cgurmehar.kalra%40hcl.com%7Cb6b965fa945e4a7f9b2608d87c189df1%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0%7C637395793215924318%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=Z2SLId9kSjQhXA0SWmMMu5uEq3OHT1YX5v30OM5ckTM%3D&reserved=0>

4)In case if some node from baseline can't be started (e.g because its data on 
the disk was destroyed) it should be removed from baseline:

https://www.gridgain.com/docs/latest/administrators-guide/control-script#removing-nodes-from-baseline-topology<https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.gridgain.com%2Fdocs%2Flatest%2Fadministrators-guide%2Fcontrol-script%23removing-nodes-from-baseline-topology&data=04%7C01%7Cgurmehar.kalra%40hcl.com%7Cb6b965fa945e4a7f9b2608d87c189df1%7C189de737c93a4f5a8b686f4ca9941912%7C0%7C0%7C637395793215924318%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&sdata=EiZeVORdR03LAr%2BUworeIBxeP3%2F3LfosUg5izvFylu0%3D&reserved=0>

If you are not using persistence, please provide additional information that 
"data is being added to the cache but not available to any of the modules." 
means:

1) How you access data
2) What do you see in the logs

BR,
Andrei
10/29/2020 4:19 PM, Gurmehar Kalra пишет:
Hi,

I have two module(Web and Engine)  and want to share data b/w the modules , but 
when I run  web and engine together , data is added to cache  but is not 
available to either of modules.
below is my ignite config, which is same in both modules

config.setActiveOnStart(true);
config.setAutoActivationEnabled(true);

config.setIgniteHome(propertyReader.getProperty("spring.ignite.storage.path"));
config.setFailureHandler(new StopNodeOrHaltFailureHandler());
config.setDataStorageConfiguration(getDataStorageConfiguration());
config.setGridLogger(new 
JavaLogger(java.util.logging.Logger.getLogger(LOG.getClass().getCanonicalName(;

Ignite ignite = Ignition.start(config);
ignite.cluster().active(true);


All Caches created have below properties |
cache.setWriteSynchronizationMode(CacheWriteSynchronizationMode.FULL_ASYNC);
cache.setAtomicityMode(CacheAtomicityMode.

Ignite Cluster Issue on 2.7.6

[Gurmehar Kalra]

Hi,

I have two module(Web and Engine)  and want to share data b/w the modules , but 
when I run  web and engine together , data is added to cache  but is not 
available to either of modules.
below is my ignite config, which is same in both modules

config.setActiveOnStart(true);
config.setAutoActivationEnabled(true);

config.setIgniteHome(propertyReader.getProperty("spring.ignite.storage.path"));
config.setFailureHandler(new StopNodeOrHaltFailureHandler());
config.setDataStorageConfiguration(getDataStorageConfiguration());
config.setGridLogger(new 
JavaLogger(java.util.logging.Logger.getLogger(LOG.getClass().getCanonicalName(;

Ignite ignite = Ignition.start(config);
ignite.cluster().active(true);


All Caches created have below properties |
cache.setWriteSynchronizationMode(CacheWriteSynchronizationMode.FULL_ASYNC);
cache.setAtomicityMode(CacheAtomicityMode.TRANSACTIONAL);
cache.setCacheMode(CacheMode.REPLICATED);
cache.setGroupName("EngineGroup");

Both Modules  are running on  IP List : 
127.0.0.1:47501,127.0.0.1:47502,127.0.0.1:47503,127.0.0.1:47504

Please suggest..
Regards,
Gurmehar Singh

::DISCLAIMER::

The contents of this e-mail and any attachment(s) are confidential and intended 
for the named recipient(s) only. E-mail transmission is not guaranteed to be 
secure or error-free as information could be intercepted, corrupted, lost, 
destroyed, arrive late or incomplete, or may contain viruses in transmission. 
The e mail and its contents (with or without referred errors) shall therefore 
not attach any liability on the originator or HCL or its affiliates. Views or 
opinions, if any, presented in this email are solely those of the author and 
may not necessarily reflect the views or opinions of HCL or its affiliates. Any 
form of reproduction, dissemination, copying, disclosure, modification, 
distribution and / or publication of this message without the prior written 
consent of authorized representative of HCL is strictly prohibited. If you have 
received this email in error please delete it and notify the sender 
immediately. Before opening any email and/or attachments, please check them for 
viruses and other defects.