Loading...

XML

Word

Printable

Blocked:
False
Blocked Reason:
None
Ready:
False
Target Release:

8.0.z.GA
Test Coverage:

+
Steps to Reproduce:
Hide

Prepare a balancer and 4 nodes

Select one node and configure it to be a hot standby node:

<subsystem xmlns="urn:jboss:domain:modcluster:6.0"> <proxy name="default" advertise-socket="modcluster" auto-enable-contexts="true" listener="ajp"> <simple-load-provider factor="0"/> </proxy> </subsystem>

Make a request to the cluster and make a note which node was used to route the request

Disable this node

Make other request - this request should never be routed to hot standby node but it is...
Show
Prepare a balancer and 4 nodes Select one node and configure it to be a hot standby node: <subsystem xmlns= "urn:jboss:domain:modcluster:6.0" > <proxy name= "default" advertise-socket= "modcluster" auto-enable-contexts= "true" listener= "ajp" > <simple-load-provider factor= "0" /> </proxy> </subsystem> Make a request to the cluster and make a note which node was used to route the request Disable this node Make other request - this request should never be routed to hot standby node but it is...

Expected behavior: No requests should be routed to hot standby node until there are "regular" nodes in the cluster. See https://access.redhat.com/solutions/55175

Actual behavior: Hot standby node is used whenever any node in the cluster is not available anymore

This seems to be already in 7.4