[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 commented on ISPN-5889:
-----------------------------------------------
Matej Čimbora <mcimbora(a)redhat.com> changed the Status of [bug 1274155|https://bugzilla.redhat.com/show_bug.cgi?id=1274155] from ON_QA to VERIFIED
> 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: Dan Berindei
> Fix For: 8.1.0.CR1, 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)
10 years, 4 months
[JBoss JIRA] (ISPN-5879) XSite client failover - ensure TcpTransportFactory.trySwitchCluster thread safety
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-5879?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-5879:
-----------------------------------------------
Matej Čimbora <mcimbora(a)redhat.com> changed the Status of [bug 1273795|https://bugzilla.redhat.com/show_bug.cgi?id=1273795] from ON_QA to VERIFIED
> XSite client failover - ensure TcpTransportFactory.trySwitchCluster thread safety
> ---------------------------------------------------------------------------------
>
> Key: ISPN-5879
> URL: https://issues.jboss.org/browse/ISPN-5879
> Project: Infinispan
> Issue Type: Bug
> Components: Cross-Site Replication, Remote Protocols
> Reporter: Matej Čimbora
> Assignee: Galder Zamarreño
> Priority: Critical
> Fix For: 8.1.0.CR1
>
>
> When reusing a HotRod client with several threads, site can be accidentally switched multiple times by threads invoking TcpTransportFactory.trySwitchCluster. This occurs when the threads attain 'maxRetries' limit at the same time, each of them being able to invoke TcpTransportFactory..updateServers with different 'clusterAddresses' parameter. This can lead to unpredictable result (e.g. switching back to failed cluster, while the other one (backup) is up and running).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (ISPN-4905) Remove standalone mode from the server distribution
by Alan Field (JIRA)
[ https://issues.jboss.org/browse/ISPN-4905?page=com.atlassian.jira.plugin.... ]
Alan Field closed ISPN-4905.
----------------------------
Resolution: Won't Fix
It's never going away...
> Remove standalone mode from the server distribution
> ---------------------------------------------------
>
> Key: ISPN-4905
> URL: https://issues.jboss.org/browse/ISPN-4905
> Project: Infinispan
> Issue Type: Bug
> Components: Server
> Affects Versions: 7.0.0.CR2
> Reporter: Alan Field
>
> The server currently contains a standalone and clustered mode. The standalone mode can be used for development, but clustered is usually used in production. Removing standalone mode and using a single clustered node for development would mean that the development and production environments are closer to each other and would remove the need to test and verify the standalone mode.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months