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 <satyajit.man...@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 <ptupit...@apache.org>
> *Sent:* Tuesday, June 27, 2023 8:13 PM
> *To:* Mandal, Satyajit: IT (PUN) <satyajit.man...@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 -
> ptupit...@apache.org Do not click on links, open attachments, or respond
> unless you recognize the sender and can validate the content is safe.
>
> Hi Satyajit,
>
>
>
> > 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 <satyajit.man...@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.
>

Reply via email to