Bug 988675 - HotRod Client recieves stale toplogy view on instance leave
Summary: HotRod Client recieves stale toplogy view on instance leave
Keywords:
Status: ASSIGNED
Alias: None
Product: JBoss Data Grid 6
Classification: JBoss
Component: Server
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ER5
: 6.2.0
Assignee: Tristan Tarrant
QA Contact: Martin Gencur
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-07-26 06:22 UTC by Takayoshi Kimura
Modified: 2014-09-10 10:59 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
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 09:33 UTC, Alan Field 		no flags Details
JDG 6.3.1 ER2 HotRod protocol 2.0 log (87.28 KB, text/plain)
2014-09-10 09:34 UTC, Alan Field 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker ISPN-3223 0 Major Resolved HotRod 2.0 Client recieves stale toplogy view on instance leave 2020-06-22 05:12:09 UTC

Description Takayoshi Kimura 2013-07-26 06:22:58 UTC 
Product ticket for ISPN-3223
Comment 2 Alan Field 2014-09-10 09:33:51 UTC 
Created attachment 936081 [details]
JDG 6.3.1 ER2 HotRod protocol 1.3 log
Comment 3 Alan Field 2014-09-10 09:34:41 UTC 
Created attachment 936083 [details]
JDG 6.3.1 ER2 HotRod protocol 2.0 log
Comment 4 Alan Field 2014-09-10 10:34:34 UTC 
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 5 Alan Field 2014-09-10 10:59:55 UTC 
(In reply to Alan Field from comment #4)
> 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.

Moved these comments and attachments to a new BZ-1140123
Note You need to log in before you can comment on or make changes to this bug.