Bug 988675
| Summary: | HotRod Client recieves stale toplogy view on instance leave | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Data Grid 6 | Reporter: | Takayoshi Kimura <tkimura> | ||||||
| Component: | Server | Assignee: | Tristan Tarrant <ttarrant> | ||||||
| Status: | CLOSED EOL | QA Contact: | Martin Gencur <mgencur> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | medium | ||||||||
| Version: | 6.1.0 | CC: | afield, jdg-bugs | ||||||
| Target Milestone: | ER5 | ||||||||
| Target Release: | 6.2.0 | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2024-05-01 00:20:57 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: |
|
||||||||
|
Description
Takayoshi Kimura
2013-07-26 06:22:58 UTC
Created attachment 936081 [details]
JDG 6.3.1 ER2 HotRod protocol 1.3 log
Created attachment 936083 [details]
JDG 6.3.1 ER2 HotRod protocol 2.0 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. (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 |