[
https://issues.jboss.org/browse/ISPN-2550?page=com.atlassian.jira.plugin....
]
Dan Berindei commented on ISPN-2550:
------------------------------------
The IndexOutOfBoundsException seems to appear because we're generating numOwners (2)
"denormalized" hash ids for each segment, but the consistent hash has more than
owners for one segment (3). This can happen during a join, when the write CH is a union
between the previous CH and the new, balanced, CH.
Tomas, I've updated my branch to use the read CH instead, could you try again?
NoSuchElementException in Hot Rod Encoder
-----------------------------------------
Key: ISPN-2550
URL:
https://issues.jboss.org/browse/ISPN-2550
Project: Infinispan
Issue Type: Bug
Components: Remote protocols
Affects Versions: 5.2.0.Beta4
Reporter: Michal Linhard
Assignee: Galder ZamarreƱo
Priority: Blocker
Fix For: 5.2.0.Beta6
Tomas noticed this a while ago in a specific functional test:
https://bugzilla.redhat.com/show_bug.cgi?id=875151
I'm creating a more general JIRA, cause I'm having this in resilience test.
What I found by quick debug, is that here:
https://github.com/infinispan/infinispan/blob/master/server/hotrod/src/ma...
{code}
for (segmentIdx <- 0 until numSegments) {
val denormalizedSegmentHashIds = allDenormalizedHashIds(segmentIdx)
val segmentOwners = ch.locateOwnersForSegment(segmentIdx)
for (ownerIdx <- 0 until segmentOwners.length) {
val address = segmentOwners(ownerIdx % segmentOwners.size)
val serverAddress = members(address)
val hashId = denormalizedSegmentHashIds(ownerIdx)
log.tracef("Writing hash id %d for %s:%s", hashId,
serverAddress.host, serverAddress.port)
writeString(serverAddress.host, buf)
writeUnsignedShort(serverAddress.port, buf)
buf.writeInt(hashId)
}
}
{code}
we're trying to obtain serverAddress for nonexistent address and
NoSuchElementException is not handled properly.
It hapens after I kill a node in a resilience test and the exception appears when
querying for the node in the members cache.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira