[infinispan-issues] [JBoss JIRA] (ISPN-2319) Add ability to take a site offline into x-site implementation

[Mircea Markus (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-2319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12721805#comment-12721805 ] 

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