6:02 p.m.
Erik Salter created ISPN-2319:
---------------------------------
Summary: Add ability to take a site offline into x-site implementation
Key: ISPN-2319
URL: https://issues.jboss.org/browse/ISPN-2319
Project: Infinispan
Issue Type: Enhancement
Components: Core API
Affects Versions: 5.2.0.Alpha3
Reporter: Erik Salter
Assignee: Mircea Markus
There should be a configuration option which determines after how many SITE-UNREACHABLE
events (combined with a timeout), a site is declared as offline. (The count should be
reset when there is a successful RPC to the remote site).
Once a site is taken offline, then no RPCs would be sent to it, until it is taken online
again (manually, by a sysadmin), and the state transfer has completed.
--
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:49 a.m.
[
https://issues.jboss.org/browse/ISPN-2319?page=com.atlassian.jira.plugin....
]
Galder Zamarreño updated ISPN-2319:
-----------------------------------
Fix Version/s: 5.2.0.CR1
Component/s: Configuration
Distributed Cache
(was: Core API)
Add ability to take a site offline into x-site implementation
-------------------------------------------------------------
Key: ISPN-2319
URL: https://issues.jboss.org/browse/ISPN-2319
Project: Infinispan
Issue Type: Enhancement
Components: Configuration, Distributed Cache
Affects Versions: 5.2.0.Alpha3
Reporter: Erik Salter
Assignee: Mircea Markus
Fix For: 5.2.0.CR1
There should be a configuration option which determines after how many SITE-UNREACHABLE
events (combined with a timeout), a site is declared as offline. (The count should be
reset when there is a successful RPC to the remote site).
Once a site is taken offline, then no RPCs would be sent to it, until it is taken online
again (manually, by a sysadmin), and the state transfer has completed.
--
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:51 a.m.
[
https://issues.jboss.org/browse/ISPN-2319?page=com.atlassian.jira.plugin....
]
Galder Zamarreño updated ISPN-2319:
-----------------------------------
Component/s: Cross-Site Replication
(was: Distributed Cache)
Add ability to take a site offline into x-site implementation
-------------------------------------------------------------
Key: ISPN-2319
URL: https://issues.jboss.org/browse/ISPN-2319
Project: Infinispan
Issue Type: Enhancement
Components: Configuration, Cross-Site Replication
Affects Versions: 5.2.0.Alpha3
Reporter: Erik Salter
Assignee: Mircea Markus
Fix For: 5.2.0.CR1
There should be a configuration option which determines after how many SITE-UNREACHABLE
events (combined with a timeout), a site is declared as offline. (The count should be
reset when there is a successful RPC to the remote site).
Once a site is taken offline, then no RPCs would be sent to it, until it is taken online
again (manually, by a sysadmin), and the state transfer has completed.
--
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
3:03 p.m.
[
https://issues.jboss.org/browse/ISPN-2319?page=com.atlassian.jira.plugin....
]
Mircea Markus updated ISPN-2319:
--------------------------------
Fix Version/s: 5.2.0.Beta1
(was: 5.2.0.CR1)
Add ability to take a site offline into x-site implementation
-------------------------------------------------------------
Key: ISPN-2319
URL: https://issues.jboss.org/browse/ISPN-2319
Project: Infinispan
Issue Type: Enhancement
Components: Configuration, Cross-Site Replication
Affects Versions: 5.2.0.Alpha3
Reporter: Erik Salter
Assignee: Mircea Markus
Fix For: 5.2.0.Beta1
There should be a configuration option which determines after how many SITE-UNREACHABLE
events (combined with a timeout), a site is declared as offline. (The count should be
reset when there is a successful RPC to the remote site).
Once a site is taken offline, then no RPCs would be sent to it, until it is taken online
again (manually, by a sysadmin), and the state transfer has completed.
--
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 p.m.
[
https://issues.jboss.org/browse/ISPN-2319?page=com.atlassian.jira.plugin....
]
Mircea Markus updated ISPN-2319:
--------------------------------
Priority: Critical (was: Major)
Add ability to take a site offline into x-site implementation
-------------------------------------------------------------
Key: ISPN-2319
URL: https://issues.jboss.org/browse/ISPN-2319
Project: Infinispan
Issue Type: Enhancement
Components: Configuration, Cross-Site Replication
Affects Versions: 5.2.0.Alpha3
Reporter: Erik Salter
Assignee: Mircea Markus
Priority: Critical
Fix For: 5.2.0.Beta1
There should be a configuration option which determines after how many SITE-UNREACHABLE
events (combined with a timeout), a site is declared as offline. (The count should be
reset when there is a successful RPC to the remote site).
Once a site is taken offline, then no RPCs would be sent to it, until it is taken online
again (manually, by a sysadmin), and the state transfer has completed.
--
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 p.m.
[
https://issues.jboss.org/browse/ISPN-2319?page=com.atlassian.jira.plugin....
]
Mircea Markus updated ISPN-2319:
--------------------------------
Priority: Blocker (was: Critical)
Add ability to take a site offline into x-site implementation
-------------------------------------------------------------
Key: ISPN-2319
URL: https://issues.jboss.org/browse/ISPN-2319
Project: Infinispan
Issue Type: Enhancement
Components: Configuration, Cross-Site Replication
Affects Versions: 5.2.0.Alpha3
Reporter: Erik Salter
Assignee: Mircea Markus
Priority: Blocker
Fix For: 5.2.0.Beta1
There should be a configuration option which determines after how many SITE-UNREACHABLE
events (combined with a timeout), a site is declared as offline. (The count should be
reset when there is a successful RPC to the remote site).
Once a site is taken offline, then no RPCs would be sent to it, until it is taken online
again (manually, by a sysadmin), and the state transfer has completed.
--
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
2:52 p.m.
[
https://issues.jboss.org/browse/ISPN-2319?page=com.atlassian.jira.plugin....
]
Mircea Markus commented on ISPN-2319:
-------------------------------------
I'm thinking for the configuration to look like this:
{code:xml}
<backup failuresTillUnreachable="10"/>
{code}
Wdyt?
Add ability to take a site offline into x-site implementation
-------------------------------------------------------------
Key: ISPN-2319
URL: https://issues.jboss.org/browse/ISPN-2319
Project: Infinispan
Issue Type: Enhancement
Components: Configuration, Cross-Site Replication
Affects Versions: 5.2.0.Alpha3
Reporter: Erik Salter
Assignee: Mircea Markus
Priority: Blocker
Fix For: 5.2.0.Beta1
There should be a configuration option which determines after how many SITE-UNREACHABLE
events (combined with a timeout), a site is declared as offline. (The count should be
reset when there is a successful RPC to the remote site).
Once a site is taken offline, then no RPCs would be sent to it, until it is taken online
again (manually, by a sysadmin), and the state transfer has completed.
--
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
3:09 p.m.
[
https://issues.jboss.org/browse/ISPN-2319?page=com.atlassian.jira.plugin....
]
Mircea Markus commented on ISPN-2319:
-------------------------------------
as [~belaban] suggested, iff only the failure policy is "FAIL" a site would be
marked as offline after a failuresTillUnreachable number of unreachable responses.
Add ability to take a site offline into x-site implementation
-------------------------------------------------------------
Key: ISPN-2319
URL: https://issues.jboss.org/browse/ISPN-2319
Project: Infinispan
Issue Type: Enhancement
Components: Configuration, Cross-Site Replication
Affects Versions: 5.2.0.Alpha3
Reporter: Erik Salter
Assignee: Mircea Markus
Priority: Blocker
Fix For: 5.2.0.Beta1
There should be a configuration option which determines after how many SITE-UNREACHABLE
events (combined with a timeout), a site is declared as offline. (The count should be
reset when there is a successful RPC to the remote site).
Once a site is taken offline, then no RPCs would be sent to it, until it is taken online
again (manually, by a sysadmin), and the state transfer has completed.
--
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
3:11 p.m.
[
https://issues.jboss.org/browse/ISPN-2319?page=com.atlassian.jira.plugin....
]
Mircea Markus commented on ISPN-2319:
-------------------------------------
JGroisp::UnicastRequets.getValue -> shows all the exception that might need to be
handled.
Add ability to take a site offline into x-site implementation
-------------------------------------------------------------
Key: ISPN-2319
URL: https://issues.jboss.org/browse/ISPN-2319
Project: Infinispan
Issue Type: Enhancement
Components: Configuration, Cross-Site Replication
Affects Versions: 5.2.0.Alpha3
Reporter: Erik Salter
Assignee: Mircea Markus
Priority: Blocker
Fix For: 5.2.0.Beta1
There should be a configuration option which determines after how many SITE-UNREACHABLE
events (combined with a timeout), a site is declared as offline. (The count should be
reset when there is a successful RPC to the remote site).
Once a site is taken offline, then no RPCs would be sent to it, until it is taken online
again (manually, by a sysadmin), and the state transfer has completed.
--
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
3:49 p.m.
[
https://issues.jboss.org/browse/ISPN-2319?page=com.atlassian.jira.plugin....
]
Mircea Markus edited comment on ISPN-2319 at 9/25/12 9:47 AM:
--------------------------------------------------------------
A site would be taken offline disregarding the failure policy (FAILURE, WARN, IGNORE) and
the replication mode (SYNC, ASYNC).
This is because even for async replication, a call for a failed site might not return
immediately because of the retry logic in RELAY2.
was (Author: mircea.markus):
as [~belaban] suggested, iff only the failure policy is "FAIL" a site would
be marked as offline after a failuresTillUnreachable number of unreachable responses.
Add ability to take a site offline into x-site implementation
-------------------------------------------------------------
Key: ISPN-2319
URL: https://issues.jboss.org/browse/ISPN-2319
Project: Infinispan
Issue Type: Enhancement
Components: Configuration, Cross-Site Replication
Affects Versions: 5.2.0.Alpha3
Reporter: Erik Salter
Assignee: Mircea Markus
Priority: Blocker
Fix For: 5.2.0.Beta1
There should be a configuration option which determines after how many SITE-UNREACHABLE
events (combined with a timeout), a site is declared as offline. (The count should be
reset when there is a successful RPC to the remote site).
Once a site is taken offline, then no RPCs would be sent to it, until it is taken online
again (manually, by a sysadmin), and the state transfer has completed.
--
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:06 p.m.
[
https://issues.jboss.org/browse/ISPN-2319?page=com.atlassian.jira.plugin....
]
Mircea Markus edited comment on ISPN-2319 at 9/25/12 11:05 AM:
---------------------------------------------------------------
I'm thinking for the configuration to look like this:
{code:xml}
<backup failuresTillUnreachable="10"/>
{code}
Wdyt?
was (Author: mircea.markus):
I'm thinking for the configuration to look like this:
{code:xml}
<backup failuresTillUnreachable="10"/>
{code}
Wdyt?
Add ability to take a site offline into x-site implementation
-------------------------------------------------------------
Key: ISPN-2319
URL: https://issues.jboss.org/browse/ISPN-2319
Project: Infinispan
Issue Type: Enhancement
Components: Configuration, Cross-Site Replication
Affects Versions: 5.2.0.Alpha3
Reporter: Erik Salter
Assignee: Mircea Markus
Priority: Blocker
Fix For: 5.2.0.Beta1
There should be a configuration option which determines after how many SITE-UNREACHABLE
events (combined with a timeout), a site is declared as offline. (The count should be
reset when there is a successful RPC to the remote site).
Once a site is taken offline, then no RPCs would be sent to it, until it is taken online
again (manually, by a sysadmin), and the state transfer has completed.
--
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:06 p.m.
[
https://issues.jboss.org/browse/ISPN-2319?page=com.atlassian.jira.plugin....
]
Mircea Markus edited comment on ISPN-2319 at 9/25/12 11:05 AM:
---------------------------------------------------------------
I'm thinking for the configuration to look like this:
{code:xml}
<backup failuresTillOffline="10"/>
{code}
Wdyt?
was (Author: mircea.markus):
I'm thinking for the configuration to look like this:
{code:xml}
<backup failuresTillUnreachable="10"/>
{code}
Wdyt?
Add ability to take a site offline into x-site implementation
-------------------------------------------------------------
Key: ISPN-2319
URL: https://issues.jboss.org/browse/ISPN-2319
Project: Infinispan
Issue Type: Enhancement
Components: Configuration, Cross-Site Replication
Affects Versions: 5.2.0.Alpha3
Reporter: Erik Salter
Assignee: Mircea Markus
Priority: Blocker
Fix For: 5.2.0.Beta1
There should be a configuration option which determines after how many SITE-UNREACHABLE
events (combined with a timeout), a site is declared as offline. (The count should be
reset when there is a successful RPC to the remote site).
Once a site is taken offline, then no RPCs would be sent to it, until it is taken online
again (manually, by a sysadmin), and the state transfer has completed.
--
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
2:05 a.m.
[
https://issues.jboss.org/browse/ISPN-2319?page=com.atlassian.jira.plugin....
]
Erik Salter commented on ISPN-2319:
-----------------------------------
So the time before a site-unreachable would be "failuresUntilOffline" *
"timeout" ms?
By consequence, would this also handle the case where an async remote transaction fails
(say, due to a node failing on the remote site)? I had implemented a brute-force method
similar to:
<backup retryNum="5" retryBackoff="1000"/>
Add ability to take a site offline into x-site implementation
-------------------------------------------------------------
Key: ISPN-2319
URL: https://issues.jboss.org/browse/ISPN-2319
Project: Infinispan
Issue Type: Enhancement
Components: Configuration, Cross-Site Replication
Affects Versions: 5.2.0.Alpha3
Reporter: Erik Salter
Assignee: Mircea Markus
Priority: Blocker
Fix For: 5.2.0.Beta1
There should be a configuration option which determines after how many SITE-UNREACHABLE
events (combined with a timeout), a site is declared as offline. (The count should be
reset when there is a successful RPC to the remote site).
Once a site is taken offline, then no RPCs would be sent to it, until it is taken online
again (manually, by a sysadmin), and the state transfer has completed.
--
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
1:45 p.m.
[
https://issues.jboss.org/browse/ISPN-2319?page=com.atlassian.jira.plugin....
]
Mircea Markus commented on ISPN-2319:
-------------------------------------
[~an1310] re: the time, [~belaban] had a better suggestion: to define a minFailureTime
before which, disregarding of the number of failed operations, a site wouldn't be
marked as offline. That's because you can have N concurren transactions crashing
simultaneously, which would increase the "failuresTillOffline" counter at once.
it would be only a bridge communication error that would be considered for marking a site
as offline. Any issues raised within the other cluster, e.g. timeouts or replication
failures caused by cluster failures would not count (but would affect the transaction
outcome).
Not sure what you mean by: "<backup retryNum="5"
retryBackoff="1000"/>"...
Add ability to take a site offline into x-site implementation
-------------------------------------------------------------
Key: ISPN-2319
URL: https://issues.jboss.org/browse/ISPN-2319
Project: Infinispan
Issue Type: Enhancement
Components: Configuration, Cross-Site Replication
Affects Versions: 5.2.0.Alpha3
Reporter: Erik Salter
Assignee: Mircea Markus
Priority: Blocker
Fix For: 5.2.0.Beta1
There should be a configuration option which determines after how many SITE-UNREACHABLE
events (combined with a timeout), a site is declared as offline. (The count should be
reset when there is a successful RPC to the remote site).
Once a site is taken offline, then no RPCs would be sent to it, until it is taken online
again (manually, by a sysadmin), and the state transfer has completed.
--
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
1:47 p.m.
[
https://issues.jboss.org/browse/ISPN-2319?page=com.atlassian.jira.plugin....
]
Mircea Markus edited comment on ISPN-2319 at 9/26/12 7:46 AM:
--------------------------------------------------------------
I'm thinking for the configuration to look like this:
{code:xml}
<backup failuresTillOffline="10" minTimeToWait="30000"/>
{code}
Wdyt?
was (Author: mircea.markus):
I'm thinking for the configuration to look like this:
{code:xml}
<backup failuresTillOffline="10"/>
{code}
Wdyt?
Add ability to take a site offline into x-site implementation
-------------------------------------------------------------
Key: ISPN-2319
URL: https://issues.jboss.org/browse/ISPN-2319
Project: Infinispan
Issue Type: Enhancement
Components: Configuration, Cross-Site Replication
Affects Versions: 5.2.0.Alpha3
Reporter: Erik Salter
Assignee: Mircea Markus
Priority: Blocker
Fix For: 5.2.0.Beta1
There should be a configuration option which determines after how many SITE-UNREACHABLE
events (combined with a timeout), a site is declared as offline. (The count should be
reset when there is a successful RPC to the remote site).
Once a site is taken offline, then no RPCs would be sent to it, until it is taken online
again (manually, by a sysadmin), and the state transfer has completed.
--
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
1:59 p.m.
[
https://issues.jboss.org/browse/ISPN-2319?page=com.atlassian.jira.plugin....
]
Mircea Markus edited comment on ISPN-2319 at 9/26/12 7:57 AM:
--------------------------------------------------------------
I'm thinking for the configuration to look like this:
{code:xml}
<backup>
<takeOffline afterFailures="10" minTimeToWait="30000"/>
</backup>
{code}
Wdyt?
was (Author: mircea.markus):
I'm thinking for the configuration to look like this:
{code:xml}
<backup failuresTillOffline="10" minTimeToWait="30000"/>
{code}
Wdyt?
Add ability to take a site offline into x-site implementation
-------------------------------------------------------------
Key: ISPN-2319
URL: https://issues.jboss.org/browse/ISPN-2319
Project: Infinispan
Issue Type: Enhancement
Components: Configuration, Cross-Site Replication
Affects Versions: 5.2.0.Alpha3
Reporter: Erik Salter
Assignee: Mircea Markus
Priority: Blocker
Fix For: 5.2.0.Beta1
There should be a configuration option which determines after how many SITE-UNREACHABLE
events (combined with a timeout), a site is declared as offline. (The count should be
reset when there is a successful RPC to the remote site).
Once a site is taken offline, then no RPCs would be sent to it, until it is taken online
again (manually, by a sysadmin), and the state transfer has completed.
--
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
4:38 a.m.
[
https://issues.jboss.org/browse/ISPN-2319?page=com.atlassian.jira.plugin....
]
Mircea Markus updated ISPN-2319:
--------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/infinispan/infinispan/pull/1348
Add ability to take a site offline into x-site implementation
-------------------------------------------------------------
Key: ISPN-2319
URL: https://issues.jboss.org/browse/ISPN-2319
Project: Infinispan
Issue Type: Enhancement
Components: Configuration, Cross-Site Replication
Affects Versions: 5.2.0.Alpha3
Reporter: Erik Salter
Assignee: Mircea Markus
Priority: Blocker
Fix For: 5.2.0.Beta1
There should be a configuration option which determines after how many SITE-UNREACHABLE
events (combined with a timeout), a site is declared as offline. (The count should be
reset when there is a successful RPC to the remote site).
Once a site is taken offline, then no RPCs would be sent to it, until it is taken online
again (manually, by a sysadmin), and the state transfer has completed.
--
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:10 p.m.
[
https://issues.jboss.org/browse/ISPN-2319?page=com.atlassian.jira.plugin....
]
Mircea Markus updated ISPN-2319:
--------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
Add ability to take a site offline into x-site implementation
-------------------------------------------------------------
Key: ISPN-2319
URL: https://issues.jboss.org/browse/ISPN-2319
Project: Infinispan
Issue Type: Enhancement
Components: Configuration, Cross-Site Replication
Affects Versions: 5.2.0.Alpha3
Reporter: Erik Salter
Assignee: Mircea Markus
Priority: Blocker
Fix For: 5.2.0.Beta1
There should be a configuration option which determines after how many SITE-UNREACHABLE
events (combined with a timeout), a site is declared as offline. (The count should be
reset when there is a successful RPC to the remote site).
Once a site is taken offline, then no RPCs would be sent to it, until it is taken online
again (manually, by a sysadmin), and the state transfer has completed.
--
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
4416
days inactive
4426
days old
infinispan-issues@lists.jboss.org
17 comments
3 participants
participants (3)
-
Erik Salter (JIRA) -
Galder Zamarreño (JIRA)
-
Mircea Markus (JIRA)