Bug 1059277

Summary:	HotRod client keep trying recover a connection to a cluster member after shutdown
Product:	[JBoss] JBoss Data Grid 6	Reporter:	wfink
Component:	Infinispan	Assignee:	Tristan Tarrant <ttarrant>
Status:	VERIFIED ---	QA Contact:	Martin Gencur <mgencur>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	6.1.0	CC:	jdg-bugs, pruivo, vjuranek
Target Milestone:	CR1
Target Release:	One-off release, 6.2.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	If a Hot Rod client is connected to a server cluster and one of the servers is shutdown gracefully, the client keeps trying to reconnect to the server. This occurs in replicated mode. There is no failure from the application perspective but there is always a retry if the RoundRobin strategy returns the unavailable server. This might have impact on performance or even cause a failure if there is a larger cluster and a part is going out of work for some reason.	Story Points:	---
Clone Of:
Clones:	1135520 (view as bug list)		Environment:
Last Closed:		Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1060199, 1075061, 1060655, 1135520

Description wfink 2014-01-29 14:55:18 UTC

If a HotRod client is connected to a server cluster and one of the servers do a correct shutdown, the client keep try to reconnect the server after the cluster view has changed.
There is only a replicated cache configured.

From the server-logfile the new cluster view is established
16:00:22,290 INFO [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (Incoming-3,shared=udp) ISPN000094: Received new cluster view: [node1/clustered|2] (1) [node1/clustered]

There is no failure from the application perspective, but there there is always a retry if the RoundRobin return the unavailable server.
This might end in a performance or failure issue if there is a larger cluster and a part going out of work for some reason.

Comment 1 JBoss JIRA Server 2014-01-31 13:29:18 UTC

Pedro Ruivo <pruivo> updated the status of jira ISPN-3942 to Coding In Progress

Comment 2 wfink 2014-02-03 08:42:34 UTC

*** Bug 1059276 has been marked as a duplicate of this bug. ***

Comment 3 JBoss JIRA Server 2014-02-06 12:37:02 UTC

Radim Vansa <rvansa> updated the status of jira ISPN-3942 to Reopened

Comment 4 Radim Vansa 2014-02-21 07:30:34 UTC

The original patch did not work. The new patch (currently PR) cannot be backported.

The issue is in fact not critical, I recommend closing as can't fix for JDG 6.1