| Summary: | call to unsupported operation while using hotrod client/server access | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Data Grid 5 | Reporter: | Michal Linhard <mlinhard> |
| Component: | Infinispan | Assignee: | Default User <jbpapp-maint> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | EAP 5.1.0 EDG TP | CC: | galder.zamarreno, mlinhard, nobody, rhusar |
| Target Milestone: | --- | ||
| Target Release: | EAP 5.1.0 EDG TP | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/EDG-55 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-03-07 10:06:20 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: | |
| Bug Depends On: | |||
| Bug Blocks: | 745860 | ||
|
Description
Michal Linhard
2011-02-28 09:35:13 UTC
Hmmm, this is something that needs looking into. That UnionConsistentHash is used when rehashing is going on and a new view is being installed. It appears that the hash id for a given node cannot be calculated at that point. I'll probably need to check with Manik on this. Good catch Michal! Link: Added: This issue depends ISPN-963 today Rado also ran into this problem when running a job: http://hudson.qa.jboss.com/hudson/view/EDG/job/edg-51x-resilience-client-size4-hotrod/6/console-perf02/ Michal/Rado, this has now been fixed and we'll release today a new CR (March 7). Can you make sure you run your tests to verify it works fine now? Marking it as resolved for the time being. Michal, CR4 is out now. Make sure you integrate and test it asap since we're targeting a Final at the end of this week. Sure, we're on it. Well, I've updated EDG to use infinispan 4.2.1.CR4 and Rado has rerun his job, we saw these exceptions in. They are not occuring, but I don't know whether this was a valid run. http://hudson.qa.jboss.com/hudson/view/EDG/job/edg-51x-resilience-client-size4-hotrod/13/ It's not currently possible to rerun my original job http://hudson.qa.jboss.com/hudson/view/EDG/job/edg-51x-stress-client-size6-hotrod/ it was only a short time for which I had perf lab machines available for size6 cluster tests. It might take a little longer till we can run such jobs again. And even then It occured only once in my run. Rado had multiple occurences of them. Since Rado is already gone, we'll try to rerun Rado's job tomorrow and verify again. Rado did another runs of his job and we didn't see the exception again http://hudson.qa.jboss.com/hudson/view/EDG/job/edg-51x-resilience-client-size4-hotrod/ I don't know how to exactly replicate this so this so we didn't verify the issue for 100%, but it seems that it's ok now. I'll run one more test with CR3 to see whether we'll see the exceptions there. unfortunately the same run with 4.2.1.CR3 didn't show the exceptions. Michal/Rado, just keep running your tests and if it appears again, we'll look into it. Link: Added: This issue is a dependency of JBPAPP-6054 |