[JBoss JIRA] (ISPN-2669) Add a Active-Passive Failover Strategy for Hot Rod client
by Ray Tsang (JIRA)
[ https://issues.jboss.org/browse/ISPN-2669?page=com.atlassian.jira.plugin.... ]
Ray Tsang commented on ISPN-2669:
---------------------------------
I implemented something according to Mircea's suggestion where the balancer will always return the first one in the server list. However, if the first server disappears, and before server is removed the server list, RetryOnFailureOperation will attempt to retry by getting the nextServer, but nextServer will always return 1st one - which will fail. In the end, RetryOnFailure will exceed the max retries and fail.
Perhaps RetryOnFailureOperation will need to tell the TransportFactory that a server had disappeared.
> Add a Active-Passive Failover Strategy for Hot Rod client
> ---------------------------------------------------------
>
> Key: ISPN-2669
> URL: https://issues.jboss.org/browse/ISPN-2669
> Project: Infinispan
> Issue Type: Feature Request
> Components: Remote protocols
> Reporter: Ray Tsang
> Assignee: Galder Zamarreño
>
> Currently HotRod client has only Round Robin request balancing strategy. There may be use cases where user needs to do an active-passive setup where all requests to go primary active node and only fallback to passive node when active is down.
--
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
12 years
[JBoss JIRA] (ISPN-2543) org.infinispan.server.memcached.MemcachedClusteredStatsTest.testSingleConnectionPerServer fails periodically on all environments
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/ISPN-2543?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on ISPN-2543:
-----------------------------------------------
Anna Manukyan <amanukya(a)redhat.com> changed the Status of [bug 879545|https://bugzilla.redhat.com/show_bug.cgi?id=879545] from ON_QA to VERIFIED
> org.infinispan.server.memcached.MemcachedClusteredStatsTest.testSingleConnectionPerServer fails periodically on all environments
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: ISPN-2543
> URL: https://issues.jboss.org/browse/ISPN-2543
> Project: Infinispan
> Issue Type: Bug
> Affects Versions: 5.2.0.Beta4
> Reporter: Anna Manukyan
> Assignee: Tristan Tarrant
> Labels: testsuite_stability
>
> org.infinispan.server.memcached.MemcachedClusteredStatsTest.testSingleConnectionPerServer test fails periodically on RHEL6_x86 and RHEL6_x86_64 - JDK7, IBM JDK7 & OpenJDK7. The test also fails on Windows 2008 64 bit with Oracle JDK 7.
> The exception is:
> {code}
> Error Message
> Unknown attribute 'NumberOfGlobalConnections'. Known attributes names are: [port, numberWorkerThreads, receiveBufferSize, totalBytesRead, numberOfGlobalConnections, idleTimeout, totalBytesWritten, hostName, numberOfLocalConnections, sendBufferSize, tpcNoDelay]
> Stacktrace
> javax.management.AttributeNotFoundException: Unknown attribute 'NumberOfGlobalConnections'. Known attributes names are: [port, numberWorkerThreads, receiveBufferSize, totalBytesRead, numberOfGlobalConnections, idleTimeout, totalBytesWritten, hostName, numberOfLocalConnections, sendBufferSize, tpcNoDelay]
> at org.infinispan.jmx.ResourceDMBean.getAttribute(ResourceDMBean.java:201)
> at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttribute(DefaultMBeanServerInterceptor.java:647)
> at com.sun.jmx.mbeanserver.JmxMBeanServer.getAttribute(JmxMBeanServer.java:668)
> at org.infinispan.server.core.ConnectionStatsTests$.testGlobalConnections(ConnectionStatsTests.scala:68)
> at org.infinispan.server.memcached.MemcachedClusteredStatsTest.testSingleConnectionPerServer(MemcachedClusteredStatsTest.scala:61)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:80)
> at org.testng.internal.Invoker.invokeMethod(Invoker.java:715)
> at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:907)
> at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1237)
> at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127)
> at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111)
> at org.testng.TestRunner.privateRun(TestRunner.java:767)
> at org.testng.TestRunner.run(TestRunner.java:617)
> at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
> at org.testng.SuiteRunner.access$000(SuiteRunner.java:37)
> at org.testng.SuiteRunner$SuiteWorker.run(SuiteRunner.java:368)
> at org.testng.internal.thread.ThreadUtil$2.call(ThreadUtil.java:64)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:722)
> {code}
--
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
12 years