[
https://issues.jboss.org/browse/ISPN-2332?page=com.atlassian.jira.plugin....
]
Bela Ban commented on ISPN-2332:
--------------------------------
Why not both ? Allow backup strategies to be defined globally, and override them on a
per-cache basis. An empty <backups/> or <sites/> means we don't back up a
named cache...
This would allow for the following:
- If we want almost all caches to be backed up: define the strategies in the global
section and override the named caches that should not get backed up with an empty
<backups/>
- If we have predominantly local, non-backed up caches, don't define <backups>
in the global section, but instead on a per cache basis.
Update xsite configuration file
-------------------------------
Key: ISPN-2332
URL:
https://issues.jboss.org/browse/ISPN-2332
Project: Infinispan
Issue Type: Feature Request
Components: Cross-Site Replication
Affects Versions: 5.2.0.Alpha4
Reporter: Mircea Markus
Assignee: Mircea Markus
Priority: Blocker
Fix For: 5.2.0.Beta1
Update configuration file after feedback:
{code:xml}
<sites local="LON">
<site name="SFO"/>
<site name="NYC"/>
<site name="LON"/>
</sites>
{code}
The sites element above are not used and should be dropped.
Also the local configuration should look like:
{code:xml}
<global>
<sites>
<localSite="${site:LON}"
backupSites="${backup-sites:SFO,NYC}" />
<backups>
<backup site="NYC" backupFailurePolicy="WARN"
strategy="SYNC" timeout="12000"/>
<backup site="SFO" backupFailurePolicy="IGNORE"
strategy="ASYNC"/>
<backup site="LON" backupFailurePolicy="IGNORE"
strategy="ASYNC"/>
</backups>
</sites>
</global>
{code}
This would allow re-using of configuration files between sites.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira