[ 
https://issues.apache.org/jira/browse/IGNITE-9365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16618233#comment-16618233
 ] 

Valentin Kulichenko commented on IGNITE-9365:
---------------------------------------------

Hi [~syssoftsol]. The change looks OK to me, although I'm not sure about the 
way you handle null values. I don't think there should be anything special 
about them - if both are nulls, then it's a match, otherwise it's not. Said 
that, I think it's better to just get attribute values from both nodes and use 
{{Objects.equals}} that already takes null values into account. That would 
simplify the logic and make it more intuitive in my view. Do you agree?

> Force backups to different AWS availability zones using only Spring XML
> -----------------------------------------------------------------------
>
>                 Key: IGNITE-9365
>                 URL: https://issues.apache.org/jira/browse/IGNITE-9365
>             Project: Ignite
>          Issue Type: Improvement
>          Components: cache
>         Environment:  
>            Reporter: David Harvey
>            Assignee: David Harvey
>            Priority: Minor
>             Fix For: 2.7
>
>         Attachments: master_947962f785_availability_zones_via_spring.patch
>
>   Original Estimate: 168h
>  Remaining Estimate: 168h
>
> As a developer, I want to be able to force  cache backups each to a different 
> "Availability Zone", when I'm running out-of-the-box Ignite, without 
> additional Jars installed.  "Availability zone" is a AWS feature with 
> different names for the same function by other cloud providers.  A single 
> availability zone has the characteristic that some or all of the EC2 
> instances in that zone can fail together due to a single fault.   You have no 
> control over the hosts on which the EC2 instance VMs run on in AWS, except by 
> controlling the availability zone .  
>  
> I could write a few lines of a custom affinityBackupFilter, and configure it 
> a RendezvousAffinityFunction, but then I have to get it deployed on all nodes 
> in the cluster, and peer class loading will not work to this.   The code to 
> do this should just be part of Ignite. 
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to