Bug 1140123
| Summary: | On leave, Hot Rod client ends up with old cluster formation | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Data Grid 6 | Reporter: | Alan Field <afield> | ||||||
| Component: | Server | Assignee: | Tristan Tarrant <ttarrant> | ||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Martin Gencur <mgencur> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 6.3.0, 6.3.1 | CC: | afield, dmehra, jdg-bugs, mhusnain | ||||||
| Target Milestone: | ER3 | ||||||||
| Target Release: | 6.4.0 | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2015-01-28 13:27:54 UTC | 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: | |||||||||
| Attachments: |
|
||||||||
Created attachment 936098 [details]
JDG 6.3.1 ER2 HotRod protocol 2.0 log
This bug has been fixed in JDG 6.4. Setting to ON_QA and removing requires_doc_text flag Verified in JDG 6.4.0 ER5 with both 1.3 and 2.0 protocols |
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.