[
https://issues.apache.org/jira/browse/IGNITE-9365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16619011#comment-16619011
]
David Harvey commented on IGNITE-9365:
--------------------------------------
The misspelling of the attribute name would seem to be the common error.
Having this silently suppress all backups seems wrong. It would be slightly
less wrong to silently act as if the filter was not specified, but I guess it
is still wrong.
To have an exception thrown in the filter do reasonable things, there would
need to be rework of the RendezvousAffinityFunction, which seems excessive.
Is there precedent for exceptions like this that would take down all nodes at
the time the first cache with backups is created?
Logging seems like the best alternative. Logging warnings in the filter each
time would flood the logs, but I guess that would get it noticed. Logging an
error in the filter the first time would be the other choice. What would the
right mechanism be to get a logger available in the filter's constructor?
> 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)
