10:37 a.m.
Mircea Markus created ISPN-2332:
-----------------------------------
Summary: 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
11:48 a.m.
[
https://issues.jboss.org/browse/ISPN-2332?page=com.atlassian.jira.plugin....
]
Bela Ban commented on ISPN-2332:
--------------------------------
Before you get started, let me experiment a bit more with this, and I might have more
feedback for you...
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
5:11 a.m.
[
https://issues.jboss.org/browse/ISPN-2332?page=com.atlassian.jira.plugin....
]
Mircea Markus commented on ISPN-2332:
-------------------------------------
thanks Bela. Thinking about it a bit more, I wouldn't like the backups to be defined
in the "global" section but each cache to do that in its own config, as there
might be caches that don't backup data (in-site caches). More concrete here is what I
have in mind:
{code:xml}
<global>
<sites local="LON"/>
</global>
<namedCache name="aCache">
<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>
</namedCache>
{code}
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
5:13 a.m.
[
https://issues.jboss.org/browse/ISPN-2332?page=com.atlassian.jira.plugin....
]
Mircea Markus edited comment on ISPN-2332 at 9/25/12 5:12 AM:
--------------------------------------------------------------
thanks Bela. Thinking about it a bit more, I wouldn't like the backups to be defined
in the "global" section but each cache to do that in its own config, as there
might be caches that don't backup data (in-site caches). More concrete here is what I
have in mind:
{code:xml}
<global>
<sites local="${site:LON}"/>
</global>
<namedCache name="aCache">
<sites>
<backups backupSites="${backup-sites:SFO,NYC}>
<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>
</namedCache>
{code}
was (Author: mircea.markus):
thanks Bela. Thinking about it a bit more, I wouldn't like the backups to be
defined in the "global" section but each cache to do that in its own config, as
there might be caches that don't backup data (in-site caches). More concrete here is
what I have in mind:
{code:xml}
<global>
<sites local="LON"/>
</global>
<namedCache name="aCache">
<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>
</namedCache>
{code}
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
5:21 a.m.
[
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
9:22 p.m.
[
https://issues.jboss.org/browse/ISPN-2332?page=com.atlassian.jira.plugin....
]
Mircea Markus edited comment on ISPN-2332 at 9/27/12 9:02 PM:
--------------------------------------------------------------
thanks Bela. Thinking about it a bit more, I wouldn't like the backups to be defined
in the "global" section but each cache to do that in its own config, as there
might be caches that don't backup data (in-site caches). More concrete here is what I
have in mind:
{code:xml}
<global>
<sites local="${site:LON}"/>
</global>
<namedCache name="aCache">
<sites>
<backups backupSites="${backup-sites:SFO,NYC}>
<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>
</namedCache>
{code}
was (Author: mircea.markus):
thanks Bela. Thinking about it a bit more, I wouldn't like the backups to be
defined in the "global" section but each cache to do that in its own config, as
there might be caches that don't backup data (in-site caches). More concrete here is
what I have in mind:
{code:xml}
<global>
<sites local="${site:LON}"/>
</global>
<namedCache name="aCache">
<sites>
<backups activeBackups="${backup-sites:SFO,NYC}>
<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>
</namedCache>
{code}
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
9:22 p.m.
[
https://issues.jboss.org/browse/ISPN-2332?page=com.atlassian.jira.plugin....
]
Mircea Markus edited comment on ISPN-2332 at 9/27/12 9:02 PM:
--------------------------------------------------------------
thanks Bela. Thinking about it a bit more, I wouldn't like the backups to be defined
in the "global" section but each cache to do that in its own config, as there
might be caches that don't backup data (in-site caches). More concrete here is what I
have in mind:
{code:xml}
<global>
<sites local="${site:LON}"/>
</global>
<namedCache name="aCache">
<sites>
<backups activeBackups="${backup-sites:SFO,NYC}>
<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>
</namedCache>
{code}
was (Author: mircea.markus):
thanks Bela. Thinking about it a bit more, I wouldn't like the backups to be
defined in the "global" section but each cache to do that in its own config, as
there might be caches that don't backup data (in-site caches). More concrete here is
what I have in mind:
{code:xml}
<global>
<sites local="${site:LON}"/>
</global>
<namedCache name="aCache">
<sites>
<backups backupSites="${backup-sites:SFO,NYC}>
<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>
</namedCache>
{code}
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
10:43 p.m.
[
https://issues.jboss.org/browse/ISPN-2332?page=com.atlassian.jira.plugin....
]
Mircea Markus updated ISPN-2332:
--------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/infinispan/infinispan/pull/1349
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
9:03 a.m.
[
https://issues.jboss.org/browse/ISPN-2332?page=com.atlassian.jira.plugin....
]
Tristan Tarrant updated ISPN-2332:
----------------------------------
Status: Resolved (was: Pull Request Sent)
Fix Version/s: 5.2.0.Final
Resolution: Done
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, 5.2.0.Final
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
6:04 a.m.
[
https://issues.jboss.org/browse/ISPN-2332?page=com.atlassian.jira.plugin....
]
Radim Vansa commented on ISPN-2332:
-----------------------------------
I have noticed that the documentation is not updated yet
https://docs.jboss.org/author/display/ISPN/Cross+site+replication (I am not sure whether
it should be in sync with gitrepo or some other version in case of 5.2)
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, 5.2.0.Final
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
4219
days inactive
4232
days old
infinispan-issues@lists.jboss.org
9 comments
4 participants
participants (4)
-
Bela Ban (JIRA) -
Mircea Markus (JIRA)
-
Radim Vansa (JIRA)
-
Tristan Tarrant (JIRA)