You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by Pavel Tupitsyn <pt...@apache.org> on 2023/06/27 14:42:33 UTC
Re: Data consistency in Ignite and BackUp Filter in Ignite .net node
Hi Satyajit,
> ensure backup partitions of a particular node is created in
another node and not in same node
No need to do anything, this is the default behavior: backup partitions
always reside on a different node.
To put it another way: every partition has a primary node and one or more
backup nodes. All those nodes are different (given enough nodes in the
cluster).
- AffinityBackupFilter is for complex use cases when the cluster spreads
multiple racks or availability zones [1] [2]
- If you have multiple nodes per machine, consider
RendezvousAffinityFunction.ExcludeNeighbors property [3]
[1]
https://ignite.apache.org/releases/latest/dotnetdoc/api/Apache.Ignite.Core.Cache.Affinity.Rendezvous.ClusterNodeAttributeAffinityBackupFilter.html
[2]
https://www.gridgain.com/docs/latest/developers-guide/configuring-caches/managing-data-distribution#backup-filter
[3]
https://ignite.apache.org/releases/latest/dotnetdoc/api/Apache.Ignite.Core.Cache.Affinity.AffinityFunctionBase.html#Apache_Ignite_Core_Cache_Affinity_AffinityFunctionBase_ExcludeNeighbors
On Tue, Jun 27, 2023 at 4:02 PM <sa...@barclays.com> wrote:
> Hi Pavel,
>
>
>
> We are running 6 node cluster with Active Active setup. 3 nodes in
> one Datacenter and 3 in another datacenter with external cache
> store enabled for some caches and native persistence enabled for
> others. Now if we want to setup backup = 1 for in memory caches
> how that should be done to ensure backup partitions of a
> particular node is created in another node and not in same node.
> Also is there any specific settings to ensure data consistency for
> in memory caches.
>
>
>
> Can you also share how this settings can be achieved in Ignite(.NET) ( AffinityBackupFilter in RendezvousAffinityFunction)
>
>
>
> Regards
>
> Satyajit
>
>
>
> Barclays Execution Services Limited registered in England. Registered No.
> 1767980. Registered office: 1 Churchill Place, London, E14 5HP
>
> Barclays Execution Services Limited provides support and administrative
> services across Barclays group. Barclays Execution Services Limited is an
> appointed representative of Barclays Bank UK plc, Barclays Bank plc and
> Clydesdale Financial Services Limited. Barclays Bank UK plc and Barclays
> Bank plc are authorised by the Prudential Regulation Authority and
> regulated by the Financial Conduct Authority and the Prudential Regulation
> Authority. Clydesdale Financial Services Limited is authorised and
> regulated by the Financial Conduct Authority.
>
> This email and any attachments are confidential and intended solely for
> the addressee and may also be privileged or exempt from disclosure under
> applicable law. If you are not the addressee, or have received this email
> in error, please notify the sender and immediately delete it and any
> attachments from your system. Do not copy, use, disclose or otherwise act
> on any part of this email or its attachments.
>
> Internet communications are not guaranteed to be secure or virus-free. The
> Barclays group does not accept responsibility for any loss arising from
> unauthorised access to, or interference with, any internet communications
> by any third party, or from the transmission of any viruses. Replies to
> this email may be monitored by the Barclays group for operational or
> business reasons.
>
> Any opinion or other information in this email or its attachments that
> does not relate to the business of the Barclays group is personal to the
> sender and is not given or endorsed by the Barclays group.
>
> Unless specifically indicated, this e-mail is not an offer to buy or sell
> or a solicitation to buy or sell any securities, investment products or
> other financial product or service, an official confirmation of any
> transaction, or an official statement of Barclays.
>
RE: Data consistency in Ignite and BackUp Filter in Ignite .net node
Posted by "satyajit.mandal.barclays.com via user" <us...@ignite.apache.org>.
Hi Pavel,
Thanks for below Info. I need one more clarification regarding data consistency and your views.
We have a microservice based architecture where one service will update/insert the cache cluster and notify other service to read data from cache in real time way. So lookup can happen either key based or applying TextQuery search.
We have external cache store as backup but that will not help during Text Query Search as all data needs to be in memory. So do you see any issue with data consistency while querying the cache?
We will ensure sufficient memory per data region. Is there anything else which needs to be monitored . If you can share some views . We can add those metrics for monitoring?
Regards
Satyajit
From: Pavel Tupitsyn <pt...@apache.org>
Sent: Tuesday, June 27, 2023 8:13 PM
To: Mandal, Satyajit: IT (PUN) <sa...@barclays.com>
Cc: user@ignite.apache.org
Subject: Re: Data consistency in Ignite and BackUp Filter in Ignite .net node
CAUTION: This email originated from outside our organisation - ptupitsyn@apache.org<ma...@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,
> ensure backup partitions of a particular node is created in another node and not in same node
No need to do anything, this is the default behavior: backup partitions always reside on a different node.
To put it another way: every partition has a primary node and one or more backup nodes. All those nodes are different (given enough nodes in the cluster).
- AffinityBackupFilter is for complex use cases when the cluster spreads multiple racks or availability zones [1] [2]
- If you have multiple nodes per machine, consider RendezvousAffinityFunction.ExcludeNeighbors property [3]
[1] https://ignite.apache.org/releases/latest/dotnetdoc/api/Apache.Ignite.Core.Cache.Affinity.Rendezvous.ClusterNodeAttributeAffinityBackupFilter.html<https://clicktime.symantec.com/15sM1Gy5PdsLM3siGkM23?h=cO_QJLdrtzTxbFFZGD0aLyUUsqezz5X0GCiXSjqzYYg=&u=https://ignite.apache.org/releases/latest/dotnetdoc/api/Apache.Ignite.Core.Cache.Affinity.Rendezvous.ClusterNodeAttributeAffinityBackupFilter.html>
[2] https://www.gridgain.com/docs/latest/developers-guide/configuring-caches/managing-data-distribution#backup-filter<https://clicktime.symantec.com/15sM67AMrFYvkzhdpJkAf?h=-Jbv1-ZUpqMUY2xn5IJddtZ2wk_5th5Uy1TKW0AfIqU=&u=https://www.gridgain.com/docs/latest/developers-guide/configuring-caches/managing-data-distribution%23backup-filter>
[3] https://ignite.apache.org/releases/latest/dotnetdoc/api/Apache.Ignite.Core.Cache.Affinity.AffinityFunctionBase.html#Apache_Ignite_Core_Cache_Affinity_AffinityFunctionBase_ExcludeNeighbors<https://clicktime.symantec.com/15sLvSmnw2Bjw73njBwsR?h=AdE7UMHeKx0TYXHG0iydrlc2PuNzZ7b4z1rZN_ZVUjw=&u=https://ignite.apache.org/releases/latest/dotnetdoc/api/Apache.Ignite.Core.Cache.Affinity.AffinityFunctionBase.html%23Apache_Ignite_Core_Cache_Affinity_AffinityFunctionBase_ExcludeNeighbors>
On Tue, Jun 27, 2023 at 4:02 PM <sa...@barclays.com>> wrote:
Hi Pavel,
We are running 6 node cluster with Active Active setup. 3 nodes in one Datacenter and 3 in another datacenter with external cache store enabled for some caches and native persistence enabled for others. Now if we want to setup backup = 1 for in memory caches how that should be done to ensure backup partitions of a particular node is created in another node and not in same node. Also is there any specific settings to ensure data consistency for in memory caches.
Can you also share how this settings can be achieved in Ignite(.NET) ( AffinityBackupFilter in RendezvousAffinityFunction)
Regards
Satyajit
Barclays Execution Services Limited registered in England. Registered No. 1767980. Registered office: 1 Churchill Place, London, E14 5HP
Barclays Execution Services Limited provides support and administrative services across Barclays group. Barclays Execution Services Limited is an appointed representative of Barclays Bank UK plc, Barclays Bank plc and Clydesdale Financial Services Limited. Barclays Bank UK plc and Barclays Bank plc are authorised by the Prudential Regulation Authority and regulated by the Financial Conduct Authority and the Prudential Regulation Authority. Clydesdale Financial Services Limited is authorised and regulated by the Financial Conduct Authority.
This email and any attachments are confidential and intended solely for the addressee and may also be privileged or exempt from disclosure under applicable law. If you are not the addressee, or have received this email in error, please notify the sender and immediately delete it and any attachments from your system. Do not copy, use, disclose or otherwise act on any part of this email or its attachments.
Internet communications are not guaranteed to be secure or virus-free. The Barclays group does not accept responsibility for any loss arising from unauthorised access to, or interference with, any internet communications by any third party, or from the transmission of any viruses. Replies to this email may be monitored by the Barclays group for operational or business reasons.
Any opinion or other information in this email or its attachments that does not relate to the business of the Barclays group is personal to the sender and is not given or endorsed by the Barclays group.
Unless specifically indicated, this e-mail is not an offer to buy or sell or a solicitation to buy or sell any securities, investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Barclays.
Barclays Execution Services Limited registered in England. Registered No. 1767980. Registered office: 1 Churchill Place, London, E14 5HP
Barclays Execution Services Limited provides support and administrative services across Barclays group. Barclays Execution Services Limited is an appointed representative of Barclays Bank UK plc, Barclays Bank plc and Clydesdale Financial Services Limited. Barclays Bank UK plc and Barclays Bank plc are authorised by the Prudential Regulation Authority and regulated by the Financial Conduct Authority and the Prudential Regulation Authority. Clydesdale Financial Services Limited is authorised and regulated by the Financial Conduct Authority.
This email and any attachments are confidential and intended solely for the addressee and may also be privileged or exempt from disclosure under applicable law. If you are not the addressee, or have received this email in error, please notify the sender and immediately delete it and any attachments from your system. Do not copy, use, disclose or otherwise act on any part of this email or its attachments.
Internet communications are not guaranteed to be secure or virus-free. The Barclays group does not accept responsibility for any loss arising from unauthorised access to, or interference with, any internet communications by any third party, or from the transmission of any viruses. Replies to this email may be monitored by the Barclays group for operational or business reasons.
Any opinion or other information in this email or its attachments that does not relate to the business of the Barclays group is personal to the sender and is not given or endorsed by the Barclays group.
Unless specifically indicated, this e-mail is not an offer to buy or sell or a solicitation to buy or sell any securities, investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Barclays.
Re: Data consistency in Ignite and BackUp Filter in Ignite .net node
Posted by Pavel Tupitsyn <pt...@apache.org>.
Could you test the simplest use case:
- In-memory cache without any persistence
- 1 backup
- WriteSynchronizationMode = FullSync
- Check count with ICache.GetSize
Then we can add other parts (persistence) one by one to see where the
problem might be.
On Thu, Dec 7, 2023 at 5:17 AM <sa...@barclays.com> wrote:
> Hi Pavel,
>
>
>
> The cluster consist of some caches using Native persistence and
> some caches connected to external cache store. BackUp = 1 is set
> for every cache.
>
> I checked the count of cache connected to external cache store
> once it was prepopulated and then stopping one node. Ignite is
> running as .NET Embedded Service.
>
>
>
> Am using Jolokia to connect to Ignite JMX metrics as Rest Api
> and checking counts? Any thoughts or alternate way to check count?
>
>
>
> Regards
>
> Satyajit
>
>
>
> *From:* Mandal, Satyajit: IT (PUN)
> *Sent:* Wednesday, December 6, 2023 11:36 AM
> *To:* Pavel Tupitsyn <pt...@apache.org>
> *Cc:* user@ignite.apache.org
> *Subject:* RE: Data consistency in Ignite and BackUp Filter in Ignite
> .net node
>
>
>
> Hi Pavel,
>
>
>
> I am using JMX Metrics to count the cache entries.
>
>
>
> Regards
>
> Satyajit
>
>
>
> *From:* Pavel Tupitsyn <pt...@apache.org>
> *Sent:* Wednesday, December 6, 2023 11:34 AM
> *To:* Mandal, Satyajit: IT (PUN) <sa...@barclays.com>
> *Cc:* user@ignite.apache.org
> *Subject:* Re: Data consistency in Ignite and BackUp Filter in Ignite
> .net node
>
>
>
> CAUTION: This email originated from outside our organisation -
> ptupitsyn@apache.org Do not click on links, open attachments, or respond
> unless you recognize the sender and can validate the content is safe.
>
> With 1 backup and 1 node loss there should not be any data loss. How do
> you count the entries?
>
>
>
> On Wed, Dec 6, 2023 at 8:00 AM <sa...@barclays.com> wrote:
>
> Hi Pavel,
>
>
>
> We did testing with BackUp = 1 and with WriteSynchronizationMode
> as PrimarySync as well as FullSync we found that when we are
> stopping one node and comparing the count we observed that count
> of cache size is not matching. There is minimal difference. So is
> it that if we lose node then there is possibility of data loss
> and can’t prevent it for in memory cluster? Cluster has 6 nodes.
>
>
>
>
>
> Regards
>
> Satyajit
>
>
>
> *From:* Pavel Tupitsyn <pt...@apache.org>
> *Sent:* Tuesday, June 27, 2023 8:13 PM
> *To:* Mandal, Satyajit: IT (PUN) <sa...@barclays.com>
> *Cc:* user@ignite.apache.org
> *Subject:* Re: Data consistency in Ignite and BackUp Filter in Ignite
> .net node
>
>
>
> CAUTION: This email originated from outside our organisation -
> ptupitsyn@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,
>
>
>
> > ensure backup partitions of a particular node is created in
> another node and not in same node
>
> No need to do anything, this is the default behavior: backup partitions
> always reside on a different node.
>
> To put it another way: every partition has a primary node and one or more
> backup nodes. All those nodes are different (given enough nodes in the
> cluster).
>
>
>
> - AffinityBackupFilter is for complex use cases when the cluster spreads
> multiple racks or availability zones [1] [2]
>
> - If you have multiple nodes per machine, consider
> RendezvousAffinityFunction.ExcludeNeighbors property [3]
>
>
>
> [1]
> https://ignite.apache.org/releases/latest/dotnetdoc/api/Apache.Ignite.Core.Cache.Affinity.Rendezvous.ClusterNodeAttributeAffinityBackupFilter.html
> <https://clicktime.symantec.com/15sM1Gy5PdsLM3siGkM23?h=cO_QJLdrtzTxbFFZGD0aLyUUsqezz5X0GCiXSjqzYYg=&u=https://ignite.apache.org/releases/latest/dotnetdoc/api/Apache.Ignite.Core.Cache.Affinity.Rendezvous.ClusterNodeAttributeAffinityBackupFilter.html>
>
> [2]
> https://www.gridgain.com/docs/latest/developers-guide/configuring-caches/managing-data-distribution#backup-filter
> <https://clicktime.symantec.com/15sM67AMrFYvkzhdpJkAf?h=-Jbv1-ZUpqMUY2xn5IJddtZ2wk_5th5Uy1TKW0AfIqU=&u=https://www.gridgain.com/docs/latest/developers-guide/configuring-caches/managing-data-distribution%23backup-filter>
>
> [3]
> https://ignite.apache.org/releases/latest/dotnetdoc/api/Apache.Ignite.Core.Cache.Affinity.AffinityFunctionBase.html#Apache_Ignite_Core_Cache_Affinity_AffinityFunctionBase_ExcludeNeighbors
> <https://clicktime.symantec.com/15sLvSmnw2Bjw73njBwsR?h=AdE7UMHeKx0TYXHG0iydrlc2PuNzZ7b4z1rZN_ZVUjw=&u=https://ignite.apache.org/releases/latest/dotnetdoc/api/Apache.Ignite.Core.Cache.Affinity.AffinityFunctionBase.html%23Apache_Ignite_Core_Cache_Affinity_AffinityFunctionBase_ExcludeNeighbors>
>
>
>
> On Tue, Jun 27, 2023 at 4:02 PM <sa...@barclays.com> wrote:
>
> Hi Pavel,
>
>
>
> We are running 6 node cluster with Active Active setup. 3 nodes in
> one Datacenter and 3 in another datacenter with external cache
> store enabled for some caches and native persistence enabled for
> others. Now if we want to setup backup = 1 for in memory caches
> how that should be done to ensure backup partitions of a
> particular node is created in another node and not in same node.
> Also is there any specific settings to ensure data consistency for
> in memory caches.
>
>
>
> Can you also share how this settings can be achieved in Ignite(.NET) ( AffinityBackupFilter in RendezvousAffinityFunction)
>
>
>
> Regards
>
> Satyajit
>
>
>
> Barclays Execution Services Limited registered in England. Registered No.
> 1767980. Registered office: 1 Churchill Place, London, E14 5HP
>
> Barclays Execution Services Limited provides support and administrative
> services across Barclays group. Barclays Execution Services Limited is an
> appointed representative of Barclays Bank UK plc, Barclays Bank plc and
> Clydesdale Financial Services Limited. Barclays Bank UK plc and Barclays
> Bank plc are authorised by the Prudential Regulation Authority and
> regulated by the Financial Conduct Authority and the Prudential Regulation
> Authority. Clydesdale Financial Services Limited is authorised and
> regulated by the Financial Conduct Authority.
>
> This email and any attachments are confidential and intended solely for
> the addressee and may also be privileged or exempt from disclosure under
> applicable law. If you are not the addressee, or have received this email
> in error, please notify the sender and immediately delete it and any
> attachments from your system. Do not copy, use, disclose or otherwise act
> on any part of this email or its attachments.
>
> Internet communications are not guaranteed to be secure or virus-free. The
> Barclays group does not accept responsibility for any loss arising from
> unauthorised access to, or interference with, any internet communications
> by any third party, or from the transmission of any viruses. Replies to
> this email may be monitored by the Barclays group for operational or
> business reasons.
>
> Any opinion or other information in this email or its attachments that
> does not relate to the business of the Barclays group is personal to the
> sender and is not given or endorsed by the Barclays group.
>
> Unless specifically indicated, this e-mail is not an offer to buy or sell
> or a solicitation to buy or sell any securities, investment products or
> other financial product or service, an official confirmation of any
> transaction, or an official statement of Barclays.
>
>
>
> Restricted - Internal
>
> Barclays Execution Services Limited registered in England. Registered No.
> 1767980. Registered office: 1 Churchill Place, London, E14 5HP
>
> Barclays Execution Services Limited provides support and administrative
> services across Barclays group. Barclays Execution Services Limited is an
> appointed representative of Barclays Bank UK plc, Barclays Bank plc and
> Clydesdale Financial Services Limited. Barclays Bank UK plc and Barclays
> Bank plc are authorised by the Prudential Regulation Authority and
> regulated by the Financial Conduct Authority and the Prudential Regulation
> Authority. Clydesdale Financial Services Limited is authorised and
> regulated by the Financial Conduct Authority.
>
> This email and any attachments are confidential and intended solely for
> the addressee and may also be privileged or exempt from disclosure under
> applicable law. If you are not the addressee, or have received this email
> in error, please notify the sender and immediately delete it and any
> attachments from your system. Do not copy, use, disclose or otherwise act
> on any part of this email or its attachments.
>
> Internet communications are not guaranteed to be secure or virus-free. The
> Barclays group does not accept responsibility for any loss arising from
> unauthorised access to, or interference with, any internet communications
> by any third party, or from the transmission of any viruses. Replies to
> this email may be monitored by the Barclays group for operational or
> business reasons.
>
> Any opinion or other information in this email or its attachments that
> does not relate to the business of the Barclays group is personal to the
> sender and is not given or endorsed by the Barclays group.
>
> Unless specifically indicated, this e-mail is not an offer to buy or sell
> or a solicitation to buy or sell any securities, investment products or
> other financial product or service, an official confirmation of any
> transaction, or an official statement of Barclays.
>
> Barclays Execution Services Limited registered in England. Registered No.
> 1767980. Registered office: 1 Churchill Place, London, E14 5HP
>
> Barclays Execution Services Limited provides support and administrative
> services across Barclays group. Barclays Execution Services Limited is an
> appointed representative of Barclays Bank UK plc, Barclays Bank plc and
> Clydesdale Financial Services Limited. Barclays Bank UK plc and Barclays
> Bank plc are authorised by the Prudential Regulation Authority and
> regulated by the Financial Conduct Authority and the Prudential Regulation
> Authority. Clydesdale Financial Services Limited is authorised and
> regulated by the Financial Conduct Authority.
>
> This email and any attachments are confidential and intended solely for
> the addressee and may also be privileged or exempt from disclosure under
> applicable law. If you are not the addressee, or have received this email
> in error, please notify the sender and immediately delete it and any
> attachments from your system. Do not copy, use, disclose or otherwise act
> on any part of this email or its attachments.
>
> Internet communications are not guaranteed to be secure or virus-free. The
> Barclays group does not accept responsibility for any loss arising from
> unauthorised access to, or interference with, any internet communications
> by any third party, or from the transmission of any viruses. Replies to
> this email may be monitored by the Barclays group for operational or
> business reasons.
>
> Any opinion or other information in this email or its attachments that
> does not relate to the business of the Barclays group is personal to the
> sender and is not given or endorsed by the Barclays group.
>
> Unless specifically indicated, this e-mail is not an offer to buy or sell
> or a solicitation to buy or sell any securities, investment products or
> other financial product or service, an official confirmation of any
> transaction, or an official statement of Barclays.
>
RE: Data consistency in Ignite and BackUp Filter in Ignite .net node
Posted by "satyajit.mandal.barclays.com via user" <us...@ignite.apache.org>.
Hi Pavel,
The cluster consist of some caches using Native persistence and some caches connected to external cache store. BackUp = 1 is set for every cache.
I checked the count of cache connected to external cache store once it was prepopulated and then stopping one node. Ignite is running as .NET Embedded Service.
Am using Jolokia to connect to Ignite JMX metrics as Rest Api and checking counts? Any thoughts or alternate way to check count?
Regards
Satyajit
From: Mandal, Satyajit: IT (PUN)
Sent: Wednesday, December 6, 2023 11:36 AM
To: Pavel Tupitsyn <pt...@apache.org>
Cc: user@ignite.apache.org
Subject: RE: Data consistency in Ignite and BackUp Filter in Ignite .net node
Hi Pavel,
I am using JMX Metrics to count the cache entries.
Regards
Satyajit
From: Pavel Tupitsyn <pt...@apache.org>>
Sent: Wednesday, December 6, 2023 11:34 AM
To: Mandal, Satyajit: IT (PUN) <sa...@barclays.com>>
Cc: user@ignite.apache.org<ma...@ignite.apache.org>
Subject: Re: Data consistency in Ignite and BackUp Filter in Ignite .net node
CAUTION: This email originated from outside our organisation - ptupitsyn@apache.org<ma...@apache.org> Do not click on links, open attachments, or respond unless you recognize the sender and can validate the content is safe.
With 1 backup and 1 node loss there should not be any data loss. How do you count the entries?
On Wed, Dec 6, 2023 at 8:00 AM <sa...@barclays.com>> wrote:
Hi Pavel,
We did testing with BackUp = 1 and with WriteSynchronizationMode as PrimarySync as well as FullSync we found that when we are stopping one node and comparing the count we observed that count of cache size is not matching. There is minimal difference. So is it that if we lose node then there is possibility of data loss and can’t prevent it for in memory cluster? Cluster has 6 nodes.
Regards
Satyajit
From: Pavel Tupitsyn <pt...@apache.org>>
Sent: Tuesday, June 27, 2023 8:13 PM
To: Mandal, Satyajit: IT (PUN) <sa...@barclays.com>>
Cc: user@ignite.apache.org<ma...@ignite.apache.org>
Subject: Re: Data consistency in Ignite and BackUp Filter in Ignite .net node
CAUTION: This email originated from outside our organisation - ptupitsyn@apache.org<ma...@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,
> ensure backup partitions of a particular node is created in another node and not in same node
No need to do anything, this is the default behavior: backup partitions always reside on a different node.
To put it another way: every partition has a primary node and one or more backup nodes. All those nodes are different (given enough nodes in the cluster).
- AffinityBackupFilter is for complex use cases when the cluster spreads multiple racks or availability zones [1] [2]
- If you have multiple nodes per machine, consider RendezvousAffinityFunction.ExcludeNeighbors property [3]
[1] https://ignite.apache.org/releases/latest/dotnetdoc/api/Apache.Ignite.Core.Cache.Affinity.Rendezvous.ClusterNodeAttributeAffinityBackupFilter.html<https://clicktime.symantec.com/15sM1Gy5PdsLM3siGkM23?h=cO_QJLdrtzTxbFFZGD0aLyUUsqezz5X0GCiXSjqzYYg=&u=https://ignite.apache.org/releases/latest/dotnetdoc/api/Apache.Ignite.Core.Cache.Affinity.Rendezvous.ClusterNodeAttributeAffinityBackupFilter.html>
[2] https://www.gridgain.com/docs/latest/developers-guide/configuring-caches/managing-data-distribution#backup-filter<https://clicktime.symantec.com/15sM67AMrFYvkzhdpJkAf?h=-Jbv1-ZUpqMUY2xn5IJddtZ2wk_5th5Uy1TKW0AfIqU=&u=https://www.gridgain.com/docs/latest/developers-guide/configuring-caches/managing-data-distribution%23backup-filter>
[3] https://ignite.apache.org/releases/latest/dotnetdoc/api/Apache.Ignite.Core.Cache.Affinity.AffinityFunctionBase.html#Apache_Ignite_Core_Cache_Affinity_AffinityFunctionBase_ExcludeNeighbors<https://clicktime.symantec.com/15sLvSmnw2Bjw73njBwsR?h=AdE7UMHeKx0TYXHG0iydrlc2PuNzZ7b4z1rZN_ZVUjw=&u=https://ignite.apache.org/releases/latest/dotnetdoc/api/Apache.Ignite.Core.Cache.Affinity.AffinityFunctionBase.html%23Apache_Ignite_Core_Cache_Affinity_AffinityFunctionBase_ExcludeNeighbors>
On Tue, Jun 27, 2023 at 4:02 PM <sa...@barclays.com>> wrote:
Hi Pavel,
We are running 6 node cluster with Active Active setup. 3 nodes in one Datacenter and 3 in another datacenter with external cache store enabled for some caches and native persistence enabled for others. Now if we want to setup backup = 1 for in memory caches how that should be done to ensure backup partitions of a particular node is created in another node and not in same node. Also is there any specific settings to ensure data consistency for in memory caches.
Can you also share how this settings can be achieved in Ignite(.NET) ( AffinityBackupFilter in RendezvousAffinityFunction)
Regards
Satyajit
Barclays Execution Services Limited registered in England. Registered No. 1767980. Registered office: 1 Churchill Place, London, E14 5HP
Barclays Execution Services Limited provides support and administrative services across Barclays group. Barclays Execution Services Limited is an appointed representative of Barclays Bank UK plc, Barclays Bank plc and Clydesdale Financial Services Limited. Barclays Bank UK plc and Barclays Bank plc are authorised by the Prudential Regulation Authority and regulated by the Financial Conduct Authority and the Prudential Regulation Authority. Clydesdale Financial Services Limited is authorised and regulated by the Financial Conduct Authority.
This email and any attachments are confidential and intended solely for the addressee and may also be privileged or exempt from disclosure under applicable law. If you are not the addressee, or have received this email in error, please notify the sender and immediately delete it and any attachments from your system. Do not copy, use, disclose or otherwise act on any part of this email or its attachments.
Internet communications are not guaranteed to be secure or virus-free. The Barclays group does not accept responsibility for any loss arising from unauthorised access to, or interference with, any internet communications by any third party, or from the transmission of any viruses. Replies to this email may be monitored by the Barclays group for operational or business reasons.
Any opinion or other information in this email or its attachments that does not relate to the business of the Barclays group is personal to the sender and is not given or endorsed by the Barclays group.
Unless specifically indicated, this e-mail is not an offer to buy or sell or a solicitation to buy or sell any securities, investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Barclays.
Restricted - Internal
Barclays Execution Services Limited registered in England. Registered No. 1767980. Registered office: 1 Churchill Place, London, E14 5HP
Barclays Execution Services Limited provides support and administrative services across Barclays group. Barclays Execution Services Limited is an appointed representative of Barclays Bank UK plc, Barclays Bank plc and Clydesdale Financial Services Limited. Barclays Bank UK plc and Barclays Bank plc are authorised by the Prudential Regulation Authority and regulated by the Financial Conduct Authority and the Prudential Regulation Authority. Clydesdale Financial Services Limited is authorised and regulated by the Financial Conduct Authority.
This email and any attachments are confidential and intended solely for the addressee and may also be privileged or exempt from disclosure under applicable law. If you are not the addressee, or have received this email in error, please notify the sender and immediately delete it and any attachments from your system. Do not copy, use, disclose or otherwise act on any part of this email or its attachments.
Internet communications are not guaranteed to be secure or virus-free. The Barclays group does not accept responsibility for any loss arising from unauthorised access to, or interference with, any internet communications by any third party, or from the transmission of any viruses. Replies to this email may be monitored by the Barclays group for operational or business reasons.
Any opinion or other information in this email or its attachments that does not relate to the business of the Barclays group is personal to the sender and is not given or endorsed by the Barclays group.
Unless specifically indicated, this e-mail is not an offer to buy or sell or a solicitation to buy or sell any securities, investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Barclays.
Barclays Execution Services Limited registered in England. Registered No. 1767980. Registered office: 1 Churchill Place, London, E14 5HP
Barclays Execution Services Limited provides support and administrative services across Barclays group. Barclays Execution Services Limited is an appointed representative of Barclays Bank UK plc, Barclays Bank plc and Clydesdale Financial Services Limited. Barclays Bank UK plc and Barclays Bank plc are authorised by the Prudential Regulation Authority and regulated by the Financial Conduct Authority and the Prudential Regulation Authority. Clydesdale Financial Services Limited is authorised and regulated by the Financial Conduct Authority.
This email and any attachments are confidential and intended solely for the addressee and may also be privileged or exempt from disclosure under applicable law. If you are not the addressee, or have received this email in error, please notify the sender and immediately delete it and any attachments from your system. Do not copy, use, disclose or otherwise act on any part of this email or its attachments.
Internet communications are not guaranteed to be secure or virus-free. The Barclays group does not accept responsibility for any loss arising from unauthorised access to, or interference with, any internet communications by any third party, or from the transmission of any viruses. Replies to this email may be monitored by the Barclays group for operational or business reasons.
Any opinion or other information in this email or its attachments that does not relate to the business of the Barclays group is personal to the sender and is not given or endorsed by the Barclays group.
Unless specifically indicated, this e-mail is not an offer to buy or sell or a solicitation to buy or sell any securities, investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Barclays.
RE: Data consistency in Ignite and BackUp Filter in Ignite .net node
Posted by "satyajit.mandal.barclays.com via user" <us...@ignite.apache.org>.
Hi Pavel,
I am using JMX Metrics to count the cache entries.
Regards
Satyajit
From: Pavel Tupitsyn <pt...@apache.org>
Sent: Wednesday, December 6, 2023 11:34 AM
To: Mandal, Satyajit: IT (PUN) <sa...@barclays.com>
Cc: user@ignite.apache.org
Subject: Re: Data consistency in Ignite and BackUp Filter in Ignite .net node
CAUTION: This email originated from outside our organisation - ptupitsyn@apache.org<ma...@apache.org> Do not click on links, open attachments, or respond unless you recognize the sender and can validate the content is safe.
With 1 backup and 1 node loss there should not be any data loss. How do you count the entries?
On Wed, Dec 6, 2023 at 8:00 AM <sa...@barclays.com>> wrote:
Hi Pavel,
We did testing with BackUp = 1 and with WriteSynchronizationMode as PrimarySync as well as FullSync we found that when we are stopping one node and comparing the count we observed that count of cache size is not matching. There is minimal difference. So is it that if we lose node then there is possibility of data loss and can’t prevent it for in memory cluster? Cluster has 6 nodes.
Regards
Satyajit
From: Pavel Tupitsyn <pt...@apache.org>>
Sent: Tuesday, June 27, 2023 8:13 PM
To: Mandal, Satyajit: IT (PUN) <sa...@barclays.com>>
Cc: user@ignite.apache.org<ma...@ignite.apache.org>
Subject: Re: Data consistency in Ignite and BackUp Filter in Ignite .net node
CAUTION: This email originated from outside our organisation - ptupitsyn@apache.org<ma...@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,
> ensure backup partitions of a particular node is created in another node and not in same node
No need to do anything, this is the default behavior: backup partitions always reside on a different node.
To put it another way: every partition has a primary node and one or more backup nodes. All those nodes are different (given enough nodes in the cluster).
- AffinityBackupFilter is for complex use cases when the cluster spreads multiple racks or availability zones [1] [2]
- If you have multiple nodes per machine, consider RendezvousAffinityFunction.ExcludeNeighbors property [3]
[1] https://ignite.apache.org/releases/latest/dotnetdoc/api/Apache.Ignite.Core.Cache.Affinity.Rendezvous.ClusterNodeAttributeAffinityBackupFilter.html<https://clicktime.symantec.com/15sM1Gy5PdsLM3siGkM23?h=cO_QJLdrtzTxbFFZGD0aLyUUsqezz5X0GCiXSjqzYYg=&u=https://ignite.apache.org/releases/latest/dotnetdoc/api/Apache.Ignite.Core.Cache.Affinity.Rendezvous.ClusterNodeAttributeAffinityBackupFilter.html>
[2] https://www.gridgain.com/docs/latest/developers-guide/configuring-caches/managing-data-distribution#backup-filter<https://clicktime.symantec.com/15sM67AMrFYvkzhdpJkAf?h=-Jbv1-ZUpqMUY2xn5IJddtZ2wk_5th5Uy1TKW0AfIqU=&u=https://www.gridgain.com/docs/latest/developers-guide/configuring-caches/managing-data-distribution%23backup-filter>
[3] https://ignite.apache.org/releases/latest/dotnetdoc/api/Apache.Ignite.Core.Cache.Affinity.AffinityFunctionBase.html#Apache_Ignite_Core_Cache_Affinity_AffinityFunctionBase_ExcludeNeighbors<https://clicktime.symantec.com/15sLvSmnw2Bjw73njBwsR?h=AdE7UMHeKx0TYXHG0iydrlc2PuNzZ7b4z1rZN_ZVUjw=&u=https://ignite.apache.org/releases/latest/dotnetdoc/api/Apache.Ignite.Core.Cache.Affinity.AffinityFunctionBase.html%23Apache_Ignite_Core_Cache_Affinity_AffinityFunctionBase_ExcludeNeighbors>
On Tue, Jun 27, 2023 at 4:02 PM <sa...@barclays.com>> wrote:
Hi Pavel,
We are running 6 node cluster with Active Active setup. 3 nodes in one Datacenter and 3 in another datacenter with external cache store enabled for some caches and native persistence enabled for others. Now if we want to setup backup = 1 for in memory caches how that should be done to ensure backup partitions of a particular node is created in another node and not in same node. Also is there any specific settings to ensure data consistency for in memory caches.
Can you also share how this settings can be achieved in Ignite(.NET) ( AffinityBackupFilter in RendezvousAffinityFunction)
Regards
Satyajit
Barclays Execution Services Limited registered in England. Registered No. 1767980. Registered office: 1 Churchill Place, London, E14 5HP
Barclays Execution Services Limited provides support and administrative services across Barclays group. Barclays Execution Services Limited is an appointed representative of Barclays Bank UK plc, Barclays Bank plc and Clydesdale Financial Services Limited. Barclays Bank UK plc and Barclays Bank plc are authorised by the Prudential Regulation Authority and regulated by the Financial Conduct Authority and the Prudential Regulation Authority. Clydesdale Financial Services Limited is authorised and regulated by the Financial Conduct Authority.
This email and any attachments are confidential and intended solely for the addressee and may also be privileged or exempt from disclosure under applicable law. If you are not the addressee, or have received this email in error, please notify the sender and immediately delete it and any attachments from your system. Do not copy, use, disclose or otherwise act on any part of this email or its attachments.
Internet communications are not guaranteed to be secure or virus-free. The Barclays group does not accept responsibility for any loss arising from unauthorised access to, or interference with, any internet communications by any third party, or from the transmission of any viruses. Replies to this email may be monitored by the Barclays group for operational or business reasons.
Any opinion or other information in this email or its attachments that does not relate to the business of the Barclays group is personal to the sender and is not given or endorsed by the Barclays group.
Unless specifically indicated, this e-mail is not an offer to buy or sell or a solicitation to buy or sell any securities, investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Barclays.
Restricted - Internal
Barclays Execution Services Limited registered in England. Registered No. 1767980. Registered office: 1 Churchill Place, London, E14 5HP
Barclays Execution Services Limited provides support and administrative services across Barclays group. Barclays Execution Services Limited is an appointed representative of Barclays Bank UK plc, Barclays Bank plc and Clydesdale Financial Services Limited. Barclays Bank UK plc and Barclays Bank plc are authorised by the Prudential Regulation Authority and regulated by the Financial Conduct Authority and the Prudential Regulation Authority. Clydesdale Financial Services Limited is authorised and regulated by the Financial Conduct Authority.
This email and any attachments are confidential and intended solely for the addressee and may also be privileged or exempt from disclosure under applicable law. If you are not the addressee, or have received this email in error, please notify the sender and immediately delete it and any attachments from your system. Do not copy, use, disclose or otherwise act on any part of this email or its attachments.
Internet communications are not guaranteed to be secure or virus-free. The Barclays group does not accept responsibility for any loss arising from unauthorised access to, or interference with, any internet communications by any third party, or from the transmission of any viruses. Replies to this email may be monitored by the Barclays group for operational or business reasons.
Any opinion or other information in this email or its attachments that does not relate to the business of the Barclays group is personal to the sender and is not given or endorsed by the Barclays group.
Unless specifically indicated, this e-mail is not an offer to buy or sell or a solicitation to buy or sell any securities, investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Barclays.
Barclays Execution Services Limited registered in England. Registered No. 1767980. Registered office: 1 Churchill Place, London, E14 5HP
Barclays Execution Services Limited provides support and administrative services across Barclays group. Barclays Execution Services Limited is an appointed representative of Barclays Bank UK plc, Barclays Bank plc and Clydesdale Financial Services Limited. Barclays Bank UK plc and Barclays Bank plc are authorised by the Prudential Regulation Authority and regulated by the Financial Conduct Authority and the Prudential Regulation Authority. Clydesdale Financial Services Limited is authorised and regulated by the Financial Conduct Authority.
This email and any attachments are confidential and intended solely for the addressee and may also be privileged or exempt from disclosure under applicable law. If you are not the addressee, or have received this email in error, please notify the sender and immediately delete it and any attachments from your system. Do not copy, use, disclose or otherwise act on any part of this email or its attachments.
Internet communications are not guaranteed to be secure or virus-free. The Barclays group does not accept responsibility for any loss arising from unauthorised access to, or interference with, any internet communications by any third party, or from the transmission of any viruses. Replies to this email may be monitored by the Barclays group for operational or business reasons.
Any opinion or other information in this email or its attachments that does not relate to the business of the Barclays group is personal to the sender and is not given or endorsed by the Barclays group.
Unless specifically indicated, this e-mail is not an offer to buy or sell or a solicitation to buy or sell any securities, investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Barclays.
Re: Data consistency in Ignite and BackUp Filter in Ignite .net node
Posted by Pavel Tupitsyn <pt...@apache.org>.
With 1 backup and 1 node loss there should not be any data loss. How do you
count the entries?
On Wed, Dec 6, 2023 at 8:00 AM <sa...@barclays.com> wrote:
> Hi Pavel,
>
>
>
> We did testing with BackUp = 1 and with WriteSynchronizationMode
> as PrimarySync as well as FullSync we found that when we are
> stopping one node and comparing the count we observed that count
> of cache size is not matching. There is minimal difference. So is
> it that if we lose node then there is possibility of data loss
> and can’t prevent it for in memory cluster? Cluster has 6 nodes.
>
>
>
>
>
> Regards
>
> Satyajit
>
>
>
> *From:* Pavel Tupitsyn <pt...@apache.org>
> *Sent:* Tuesday, June 27, 2023 8:13 PM
> *To:* Mandal, Satyajit: IT (PUN) <sa...@barclays.com>
> *Cc:* user@ignite.apache.org
> *Subject:* Re: Data consistency in Ignite and BackUp Filter in Ignite
> .net node
>
>
>
> CAUTION: This email originated from outside our organisation -
> ptupitsyn@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,
>
>
>
> > ensure backup partitions of a particular node is created in
> another node and not in same node
>
> No need to do anything, this is the default behavior: backup partitions
> always reside on a different node.
>
> To put it another way: every partition has a primary node and one or more
> backup nodes. All those nodes are different (given enough nodes in the
> cluster).
>
>
>
> - AffinityBackupFilter is for complex use cases when the cluster spreads
> multiple racks or availability zones [1] [2]
>
> - If you have multiple nodes per machine, consider
> RendezvousAffinityFunction.ExcludeNeighbors property [3]
>
>
>
> [1]
> https://ignite.apache.org/releases/latest/dotnetdoc/api/Apache.Ignite.Core.Cache.Affinity.Rendezvous.ClusterNodeAttributeAffinityBackupFilter.html
> <https://clicktime.symantec.com/15sM1Gy5PdsLM3siGkM23?h=cO_QJLdrtzTxbFFZGD0aLyUUsqezz5X0GCiXSjqzYYg=&u=https://ignite.apache.org/releases/latest/dotnetdoc/api/Apache.Ignite.Core.Cache.Affinity.Rendezvous.ClusterNodeAttributeAffinityBackupFilter.html>
>
> [2]
> https://www.gridgain.com/docs/latest/developers-guide/configuring-caches/managing-data-distribution#backup-filter
> <https://clicktime.symantec.com/15sM67AMrFYvkzhdpJkAf?h=-Jbv1-ZUpqMUY2xn5IJddtZ2wk_5th5Uy1TKW0AfIqU=&u=https://www.gridgain.com/docs/latest/developers-guide/configuring-caches/managing-data-distribution%23backup-filter>
>
> [3]
> https://ignite.apache.org/releases/latest/dotnetdoc/api/Apache.Ignite.Core.Cache.Affinity.AffinityFunctionBase.html#Apache_Ignite_Core_Cache_Affinity_AffinityFunctionBase_ExcludeNeighbors
> <https://clicktime.symantec.com/15sLvSmnw2Bjw73njBwsR?h=AdE7UMHeKx0TYXHG0iydrlc2PuNzZ7b4z1rZN_ZVUjw=&u=https://ignite.apache.org/releases/latest/dotnetdoc/api/Apache.Ignite.Core.Cache.Affinity.AffinityFunctionBase.html%23Apache_Ignite_Core_Cache_Affinity_AffinityFunctionBase_ExcludeNeighbors>
>
>
>
> On Tue, Jun 27, 2023 at 4:02 PM <sa...@barclays.com> wrote:
>
> Hi Pavel,
>
>
>
> We are running 6 node cluster with Active Active setup. 3 nodes in
> one Datacenter and 3 in another datacenter with external cache
> store enabled for some caches and native persistence enabled for
> others. Now if we want to setup backup = 1 for in memory caches
> how that should be done to ensure backup partitions of a
> particular node is created in another node and not in same node.
> Also is there any specific settings to ensure data consistency for
> in memory caches.
>
>
>
> Can you also share how this settings can be achieved in Ignite(.NET) ( AffinityBackupFilter in RendezvousAffinityFunction)
>
>
>
> Regards
>
> Satyajit
>
>
>
> Barclays Execution Services Limited registered in England. Registered No.
> 1767980. Registered office: 1 Churchill Place, London, E14 5HP
>
> Barclays Execution Services Limited provides support and administrative
> services across Barclays group. Barclays Execution Services Limited is an
> appointed representative of Barclays Bank UK plc, Barclays Bank plc and
> Clydesdale Financial Services Limited. Barclays Bank UK plc and Barclays
> Bank plc are authorised by the Prudential Regulation Authority and
> regulated by the Financial Conduct Authority and the Prudential Regulation
> Authority. Clydesdale Financial Services Limited is authorised and
> regulated by the Financial Conduct Authority.
>
> This email and any attachments are confidential and intended solely for
> the addressee and may also be privileged or exempt from disclosure under
> applicable law. If you are not the addressee, or have received this email
> in error, please notify the sender and immediately delete it and any
> attachments from your system. Do not copy, use, disclose or otherwise act
> on any part of this email or its attachments.
>
> Internet communications are not guaranteed to be secure or virus-free. The
> Barclays group does not accept responsibility for any loss arising from
> unauthorised access to, or interference with, any internet communications
> by any third party, or from the transmission of any viruses. Replies to
> this email may be monitored by the Barclays group for operational or
> business reasons.
>
> Any opinion or other information in this email or its attachments that
> does not relate to the business of the Barclays group is personal to the
> sender and is not given or endorsed by the Barclays group.
>
> Unless specifically indicated, this e-mail is not an offer to buy or sell
> or a solicitation to buy or sell any securities, investment products or
> other financial product or service, an official confirmation of any
> transaction, or an official statement of Barclays.
>
>
>
> Restricted - Internal
>
> Barclays Execution Services Limited registered in England. Registered No.
> 1767980. Registered office: 1 Churchill Place, London, E14 5HP
>
> Barclays Execution Services Limited provides support and administrative
> services across Barclays group. Barclays Execution Services Limited is an
> appointed representative of Barclays Bank UK plc, Barclays Bank plc and
> Clydesdale Financial Services Limited. Barclays Bank UK plc and Barclays
> Bank plc are authorised by the Prudential Regulation Authority and
> regulated by the Financial Conduct Authority and the Prudential Regulation
> Authority. Clydesdale Financial Services Limited is authorised and
> regulated by the Financial Conduct Authority.
>
> This email and any attachments are confidential and intended solely for
> the addressee and may also be privileged or exempt from disclosure under
> applicable law. If you are not the addressee, or have received this email
> in error, please notify the sender and immediately delete it and any
> attachments from your system. Do not copy, use, disclose or otherwise act
> on any part of this email or its attachments.
>
> Internet communications are not guaranteed to be secure or virus-free. The
> Barclays group does not accept responsibility for any loss arising from
> unauthorised access to, or interference with, any internet communications
> by any third party, or from the transmission of any viruses. Replies to
> this email may be monitored by the Barclays group for operational or
> business reasons.
>
> Any opinion or other information in this email or its attachments that
> does not relate to the business of the Barclays group is personal to the
> sender and is not given or endorsed by the Barclays group.
>
> Unless specifically indicated, this e-mail is not an offer to buy or sell
> or a solicitation to buy or sell any securities, investment products or
> other financial product or service, an official confirmation of any
> transaction, or an official statement of Barclays.
>
RE: Data consistency in Ignite and BackUp Filter in Ignite .net node
Posted by "satyajit.mandal.barclays.com via user" <us...@ignite.apache.org>.
Hi Pavel,
We did testing with BackUp = 1 and with WriteSynchronizationMode as PrimarySync as well as FullSync we found that when we are stopping one node and comparing the count we observed that count of cache size is not matching. There is minimal difference. So is it that if we lose node then there is possibility of data loss and can’t prevent it for in memory cluster? Cluster has 6 nodes.
Regards
Satyajit
From: Pavel Tupitsyn <pt...@apache.org>>
Sent: Tuesday, June 27, 2023 8:13 PM
To: Mandal, Satyajit: IT (PUN) <sa...@barclays.com>>
Cc: user@ignite.apache.org<ma...@ignite.apache.org>
Subject: Re: Data consistency in Ignite and BackUp Filter in Ignite .net node
CAUTION: This email originated from outside our organisation - ptupitsyn@apache.org<ma...@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,
> ensure backup partitions of a particular node is created in another node and not in same node
No need to do anything, this is the default behavior: backup partitions always reside on a different node.
To put it another way: every partition has a primary node and one or more backup nodes. All those nodes are different (given enough nodes in the cluster).
- AffinityBackupFilter is for complex use cases when the cluster spreads multiple racks or availability zones [1] [2]
- If you have multiple nodes per machine, consider RendezvousAffinityFunction.ExcludeNeighbors property [3]
[1] https://ignite.apache.org/releases/latest/dotnetdoc/api/Apache.Ignite.Core.Cache.Affinity.Rendezvous.ClusterNodeAttributeAffinityBackupFilter.html<https://clicktime.symantec.com/15sM1Gy5PdsLM3siGkM23?h=cO_QJLdrtzTxbFFZGD0aLyUUsqezz5X0GCiXSjqzYYg=&u=https://ignite.apache.org/releases/latest/dotnetdoc/api/Apache.Ignite.Core.Cache.Affinity.Rendezvous.ClusterNodeAttributeAffinityBackupFilter.html>
[2] https://www.gridgain.com/docs/latest/developers-guide/configuring-caches/managing-data-distribution#backup-filter<https://clicktime.symantec.com/15sM67AMrFYvkzhdpJkAf?h=-Jbv1-ZUpqMUY2xn5IJddtZ2wk_5th5Uy1TKW0AfIqU=&u=https://www.gridgain.com/docs/latest/developers-guide/configuring-caches/managing-data-distribution%23backup-filter>
[3] https://ignite.apache.org/releases/latest/dotnetdoc/api/Apache.Ignite.Core.Cache.Affinity.AffinityFunctionBase.html#Apache_Ignite_Core_Cache_Affinity_AffinityFunctionBase_ExcludeNeighbors<https://clicktime.symantec.com/15sLvSmnw2Bjw73njBwsR?h=AdE7UMHeKx0TYXHG0iydrlc2PuNzZ7b4z1rZN_ZVUjw=&u=https://ignite.apache.org/releases/latest/dotnetdoc/api/Apache.Ignite.Core.Cache.Affinity.AffinityFunctionBase.html%23Apache_Ignite_Core_Cache_Affinity_AffinityFunctionBase_ExcludeNeighbors>
On Tue, Jun 27, 2023 at 4:02 PM <sa...@barclays.com>> wrote:
Hi Pavel,
We are running 6 node cluster with Active Active setup. 3 nodes in one Datacenter and 3 in another datacenter with external cache store enabled for some caches and native persistence enabled for others. Now if we want to setup backup = 1 for in memory caches how that should be done to ensure backup partitions of a particular node is created in another node and not in same node. Also is there any specific settings to ensure data consistency for in memory caches.
Can you also share how this settings can be achieved in Ignite(.NET) ( AffinityBackupFilter in RendezvousAffinityFunction)
Regards
Satyajit
Barclays Execution Services Limited registered in England. Registered No. 1767980. Registered office: 1 Churchill Place, London, E14 5HP
Barclays Execution Services Limited provides support and administrative services across Barclays group. Barclays Execution Services Limited is an appointed representative of Barclays Bank UK plc, Barclays Bank plc and Clydesdale Financial Services Limited. Barclays Bank UK plc and Barclays Bank plc are authorised by the Prudential Regulation Authority and regulated by the Financial Conduct Authority and the Prudential Regulation Authority. Clydesdale Financial Services Limited is authorised and regulated by the Financial Conduct Authority.
This email and any attachments are confidential and intended solely for the addressee and may also be privileged or exempt from disclosure under applicable law. If you are not the addressee, or have received this email in error, please notify the sender and immediately delete it and any attachments from your system. Do not copy, use, disclose or otherwise act on any part of this email or its attachments.
Internet communications are not guaranteed to be secure or virus-free. The Barclays group does not accept responsibility for any loss arising from unauthorised access to, or interference with, any internet communications by any third party, or from the transmission of any viruses. Replies to this email may be monitored by the Barclays group for operational or business reasons.
Any opinion or other information in this email or its attachments that does not relate to the business of the Barclays group is personal to the sender and is not given or endorsed by the Barclays group.
Unless specifically indicated, this e-mail is not an offer to buy or sell or a solicitation to buy or sell any securities, investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Barclays.
Restricted - Internal
Barclays Execution Services Limited registered in England. Registered No. 1767980. Registered office: 1 Churchill Place, London, E14 5HP
Barclays Execution Services Limited provides support and administrative services across Barclays group. Barclays Execution Services Limited is an appointed representative of Barclays Bank UK plc, Barclays Bank plc and Clydesdale Financial Services Limited. Barclays Bank UK plc and Barclays Bank plc are authorised by the Prudential Regulation Authority and regulated by the Financial Conduct Authority and the Prudential Regulation Authority. Clydesdale Financial Services Limited is authorised and regulated by the Financial Conduct Authority.
This email and any attachments are confidential and intended solely for the addressee and may also be privileged or exempt from disclosure under applicable law. If you are not the addressee, or have received this email in error, please notify the sender and immediately delete it and any attachments from your system. Do not copy, use, disclose or otherwise act on any part of this email or its attachments.
Internet communications are not guaranteed to be secure or virus-free. The Barclays group does not accept responsibility for any loss arising from unauthorised access to, or interference with, any internet communications by any third party, or from the transmission of any viruses. Replies to this email may be monitored by the Barclays group for operational or business reasons.
Any opinion or other information in this email or its attachments that does not relate to the business of the Barclays group is personal to the sender and is not given or endorsed by the Barclays group.
Unless specifically indicated, this e-mail is not an offer to buy or sell or a solicitation to buy or sell any securities, investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Barclays.