[JBoss JIRA] (ISPN-5882) XSite replication - take-offline.after-failures property is ignored
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-5882?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-5882:
-----------------------------------------------
Pedro Ruivo <pruivo(a)redhat.com> changed the Status of [bug 1274800|https://bugzilla.redhat.com/show_bug.cgi?id=1274800] from NEW to POST
> XSite replication - take-offline.after-failures property is ignored
> -------------------------------------------------------------------
>
> Key: ISPN-5882
> URL: https://issues.jboss.org/browse/ISPN-5882
> Project: Infinispan
> Issue Type: Bug
> Components: Cross-Site Replication
> Reporter: Matej Čimbora
> Assignee: Pedro Ruivo
>
> Let's say I use the following backup settings and start the server in site LON:
> <backup site="BRN" strategy="SYNC">
> <take-offline after-failures="5"/>
> </backup>
> The following code snipped should cause BRN site to go offline after 5 failures, however the site is still remains online and tries to back up the data to BRN.
> RemoteCacheManager remoteCacheManager = new RemoteCacheManager();
> RemoteCache<Object, Object> cache = remoteCacheManager.getCache();
> for (int i = 0; i < 10; i++) {
> cache.put(i, i);
> }
> Server-side error message example:
> 16:05:19,121 ERROR [org.jgroups.protocols.relay.RELAY2] (HotRodServerWorker-5-2) localhost: no route to BRN: dropping message
> 16:05:29,121 WARN [org.infinispan.xsite.BackupSenderImpl] (HotRodServerWorker-5-2) ISPN000202: Problems backing up data for cache default to site BRN: org.infinispan.util.concurrent.TimeoutException: Timed out after 10 seconds waiting for a response from BRN (sync, timeout=10000)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[JBoss JIRA] (ISPN-5889) Merge views not dealt with in Hot Rod server
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/ISPN-5889?page=com.atlassian.jira.plugin.... ]
Galder Zamarreño updated ISPN-5889:
-----------------------------------
Status: Open (was: New)
> Merge views not dealt with in Hot Rod server
> --------------------------------------------
>
> Key: ISPN-5889
> URL: https://issues.jboss.org/browse/ISPN-5889
> Project: Infinispan
> Issue Type: Bug
> Components: Remote Protocols
> Affects Versions: 8.0.1.Final, 8.1.0.Alpha2
> Reporter: Galder Zamarreño
> Assignee: Galder Zamarreño
> Fix For: 8.1.0.Beta1, 8.1.0.Final
>
>
> Hot Rod server does not deal with merge views, so when members return back to the cluster, the view is not updated. The Hot Rod server view change listener currently only deals with nodes leaving or crashing. This problem is not a big one since it just means that until the next view change happens, clients will work with a reduced view, working in a suboptimal way, but it won't have correctness impact.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[JBoss JIRA] (ISPN-5889) Merge views not dealt with in Hot Rod server
by Galder Zamarreño (JIRA)
[ https://issues.jboss.org/browse/ISPN-5889?page=com.atlassian.jira.plugin.... ]
Work on ISPN-5889 started by Galder Zamarreño.
----------------------------------------------
> Merge views not dealt with in Hot Rod server
> --------------------------------------------
>
> Key: ISPN-5889
> URL: https://issues.jboss.org/browse/ISPN-5889
> Project: Infinispan
> Issue Type: Bug
> Components: Remote Protocols
> Affects Versions: 8.0.1.Final, 8.1.0.Alpha2
> Reporter: Galder Zamarreño
> Assignee: Galder Zamarreño
> Fix For: 8.1.0.Beta1, 8.1.0.Final
>
>
> Hot Rod server does not deal with merge views, so when members return back to the cluster, the view is not updated. The Hot Rod server view change listener currently only deals with nodes leaving or crashing. This problem is not a big one since it just means that until the next view change happens, clients will work with a reduced view, working in a suboptimal way, but it won't have correctness impact.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[JBoss JIRA] (ISPN-5889) Merge views not dealt with in Hot Rod server
by Galder Zamarreño (JIRA)
Galder Zamarreño created ISPN-5889:
--------------------------------------
Summary: Merge views not dealt with in Hot Rod server
Key: ISPN-5889
URL: https://issues.jboss.org/browse/ISPN-5889
Project: Infinispan
Issue Type: Bug
Components: Remote Protocols
Affects Versions: 8.1.0.Alpha2, 8.0.1.Final
Reporter: Galder Zamarreño
Assignee: Galder Zamarreño
Fix For: 8.1.0.Beta1, 8.1.0.Final
Hot Rod server does not deal with merge views, so when members return back to the cluster, the view is not updated. The Hot Rod server view change listener currently only deals with nodes leaving or crashing. This problem is not a big one since it just means that until the next view change happens, clients will work with a reduced view, working in a suboptimal way, but it won't have correctness impact.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[JBoss JIRA] (ISPN-5889) Merge views not dealt with in Hot Rod server
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-5889?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration updated ISPN-5889:
------------------------------------------
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1274155
Bugzilla Update: Perform
> Merge views not dealt with in Hot Rod server
> --------------------------------------------
>
> Key: ISPN-5889
> URL: https://issues.jboss.org/browse/ISPN-5889
> Project: Infinispan
> Issue Type: Bug
> Components: Remote Protocols
> Affects Versions: 8.0.1.Final, 8.1.0.Alpha2
> Reporter: Galder Zamarreño
> Assignee: Galder Zamarreño
> Fix For: 8.1.0.Beta1, 8.1.0.Final
>
>
> Hot Rod server does not deal with merge views, so when members return back to the cluster, the view is not updated. The Hot Rod server view change listener currently only deals with nodes leaving or crashing. This problem is not a big one since it just means that until the next view change happens, clients will work with a reduced view, working in a suboptimal way, but it won't have correctness impact.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months