Bug 1140123 - On leave, Hot Rod client ends up with old cluster formation
Summary: On leave, Hot Rod client ends up with old cluster formation
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Data Grid 6
Classification: JBoss
Component: Server
Version: 6.3.0,6.3.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ER3
: 6.4.0
Assignee: Tristan Tarrant
QA Contact: Martin Gencur
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-10 10:46 UTC by Alan Field
Modified: 2015-01-28 13:27 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-01-28 13:27:54 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
JDG 6.3.1 ER2 HotRod protocol 1.3 log (116.15 KB, text/plain)
2014-09-10 10:46 UTC, Alan Field 		no flags Details
JDG 6.3.1 ER2 HotRod protocol 2.0 log (87.28 KB, text/plain)
2014-09-10 10:46 UTC, Alan Field 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker ISPN-4707 0 Major Resolved On leave, Hot Rod client ends up with old cluster formation 2018-10-17 00:36:32 UTC

Description Alan Field 2014-09-10 10:46:00 UTC 
Created attachment 936097 [details]
JDG 6.3.1 ER2 HotRod protocol 1.3 log

The behavior with the JDG HotRod client is slightly different. After the node joins, a cluster wide rebalance occurs. If I shutdown the second node after this rebalance, then the client gets a series of exceptions before recovering. The first exception message is "Could not fetch transport", and then there are a series of "Unable to invalidate transport for server" messages for the stopped node. See the attached logs for examples.
Comment 1 Alan Field 2014-09-10 10:46:33 UTC 
Created attachment 936098 [details]
JDG 6.3.1 ER2 HotRod protocol 2.0 log
Comment 5 Alan Field 2014-11-11 15:03:27 UTC 
This bug has been fixed in JDG 6.4. Setting to ON_QA and removing requires_doc_text flag
Comment 6 Alan Field 2014-11-19 22:23:21 UTC 
Verified in JDG 6.4.0 ER5 with both 1.3 and 2.0 protocols
Note You need to log in before you can comment on or make changes to this bug.