ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Harvey (JIRA)" <j...@apache.org>
Subject [jira] [Created] (IGNITE-9365) Force backups to different AWS availability zones using only Spring XML
Date Thu, 23 Aug 2018 21:29:00 GMT
David Harvey created IGNITE-9365:
------------------------------------

             Summary: 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
             Fix For: 2.7


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)

Mime
View raw message